CWE
264
Advisory Published
CVE Published
CVE Published
Updated

CVE-2010-1170

First published: Fri Apr 16 2010(Updated: )

The PL/Tcl implementation in PostgreSQL 7.4 before 7.4.29, 8.0 before 8.0.25, 8.1 before 8.1.21, 8.2 before 8.2.17, 8.3 before 8.3.11, 8.4 before 8.4.4, and 9.0 Beta before 9.0 Beta 2 loads Tcl code from the pltcl_modules table regardless of the table's ownership and permissions, which allows remote authenticated users, with database-creation privileges, to execute arbitrary Tcl code by creating this table and inserting a crafted Tcl script.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
redhat/postgresql<0:7.4.29-1.el4_8.1
0:7.4.29-1.el4_8.1
redhat/postgresql<0:8.1.21-1.el5_5.1
0:8.1.21-1.el5_5.1
redhat/postgresql84<0:8.4.4-1.el5_5.1
0:8.4.4-1.el5_5.1
PostgreSQL JDBC Driver=7.4.16
PostgreSQL JDBC Driver=7.4.24
PostgreSQL JDBC Driver=7.4.22
PostgreSQL JDBC Driver=7.4.21
PostgreSQL JDBC Driver=7.4.19
PostgreSQL JDBC Driver=7.4.15
PostgreSQL JDBC Driver=7.4.1
PostgreSQL JDBC Driver=7.4.14
PostgreSQL JDBC Driver=7.4.26
PostgreSQL JDBC Driver=7.4.6
PostgreSQL JDBC Driver=7.4.23
PostgreSQL JDBC Driver=7.4.11
PostgreSQL JDBC Driver=7.4.7
PostgreSQL JDBC Driver=7.4.17
PostgreSQL JDBC Driver=7.4.3
PostgreSQL JDBC Driver=7.4.25
PostgreSQL JDBC Driver=7.4.9
PostgreSQL JDBC Driver=7.4.5
PostgreSQL JDBC Driver=7.4.18
PostgreSQL JDBC Driver=7.4.8
PostgreSQL JDBC Driver=7.4
PostgreSQL JDBC Driver=7.4.4
PostgreSQL JDBC Driver=7.4.28
PostgreSQL JDBC Driver=7.4.12
PostgreSQL JDBC Driver=7.4.27
PostgreSQL JDBC Driver=7.4.10
PostgreSQL JDBC Driver=7.4.20
PostgreSQL JDBC Driver=7.4.2
PostgreSQL JDBC Driver=7.4.13
PostgreSQL JDBC Driver=8.0.7
PostgreSQL JDBC Driver=8.0.2
PostgreSQL JDBC Driver=8.0.22
PostgreSQL JDBC Driver=8.0.17
PostgreSQL JDBC Driver=8.0.10
PostgreSQL JDBC Driver=8.0.12
PostgreSQL JDBC Driver=8.0.9
PostgreSQL JDBC Driver=8.0.15
PostgreSQL JDBC Driver=8.0.0
PostgreSQL JDBC Driver=8.0.18
PostgreSQL JDBC Driver=8.0.3
PostgreSQL JDBC Driver=8.0.24
PostgreSQL JDBC Driver=8.0.20
PostgreSQL JDBC Driver=8.0.8
PostgreSQL JDBC Driver=8.0.6
PostgreSQL JDBC Driver=8.0.16
PostgreSQL JDBC Driver=8.0.13
PostgreSQL JDBC Driver=8.0.1
PostgreSQL JDBC Driver=8.0.19
PostgreSQL JDBC Driver=8.0.21
PostgreSQL JDBC Driver=8.0.23
PostgreSQL JDBC Driver=8.0.4
PostgreSQL JDBC Driver=8.0.5
PostgreSQL JDBC Driver=8.0.14
PostgreSQL JDBC Driver=8.0.11
PostgreSQL JDBC Driver=8.0
PostgreSQL JDBC Driver=8.1.10
PostgreSQL JDBC Driver=8.1.6
PostgreSQL JDBC Driver=8.1.15
PostgreSQL JDBC Driver=8.1.7
PostgreSQL JDBC Driver=8.1.20
PostgreSQL JDBC Driver=8.1
PostgreSQL JDBC Driver=8.1.19
PostgreSQL JDBC Driver=8.1.13
PostgreSQL JDBC Driver=8.1.0
PostgreSQL JDBC Driver=8.1.3
PostgreSQL JDBC Driver=8.1.9
PostgreSQL JDBC Driver=8.1.14
PostgreSQL JDBC Driver=8.1.11
PostgreSQL JDBC Driver=8.1.17
PostgreSQL JDBC Driver=8.1.18
PostgreSQL JDBC Driver=8.1.4
PostgreSQL JDBC Driver=8.1.8
PostgreSQL JDBC Driver=8.1.1
PostgreSQL JDBC Driver=8.1.12
PostgreSQL JDBC Driver=8.1.5
PostgreSQL JDBC Driver=8.1.16
PostgreSQL JDBC Driver=8.1.2
PostgreSQL JDBC Driver=8.2.9
PostgreSQL JDBC Driver=8.2.10
PostgreSQL JDBC Driver=8.2.15
PostgreSQL JDBC Driver=8.2.4
PostgreSQL JDBC Driver=8.2.11
PostgreSQL JDBC Driver=8.2.12
PostgreSQL JDBC Driver=8.2.2
PostgreSQL JDBC Driver=8.2.5
PostgreSQL JDBC Driver=8.2.1
PostgreSQL JDBC Driver=8.2.7
PostgreSQL JDBC Driver=8.2.6
PostgreSQL JDBC Driver=8.2.3
PostgreSQL JDBC Driver=8.2.16
PostgreSQL JDBC Driver=8.2.8
PostgreSQL JDBC Driver=8.2.13
PostgreSQL JDBC Driver=8.2
PostgreSQL JDBC Driver=8.2.14
PostgreSQL JDBC Driver=8.3.6
PostgreSQL JDBC Driver=8.3.3
PostgreSQL JDBC Driver=8.3.2
PostgreSQL JDBC Driver=8.3.1
PostgreSQL JDBC Driver=8.3.5
PostgreSQL JDBC Driver=8.3.8
PostgreSQL JDBC Driver=8.3.7
PostgreSQL JDBC Driver=8.3.10
PostgreSQL JDBC Driver=8.3
PostgreSQL JDBC Driver=8.3.4
PostgreSQL JDBC Driver=8.3.9
PostgreSQL JDBC Driver=8.4.1
PostgreSQL JDBC Driver=8.4.3
PostgreSQL JDBC Driver=8.4
PostgreSQL JDBC Driver=8.4.2
PostgreSQL JDBC Driver=9.0.0-beta1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the severity of CVE-2010-1170?

    CVE-2010-1170 has a severity rating classified as medium due to its potential to allow unauthorized security access.

  • How do I fix CVE-2010-1170?

    To fix CVE-2010-1170, upgrade your PostgreSQL version to at least 7.4.29, 8.0.25, 8.1.21, or 8.2.17.

  • Which PostgreSQL versions are affected by CVE-2010-1170?

    CVE-2010-1170 affects PostgreSQL versions 7.4 prior to 7.4.29, 8.0 prior to 8.0.25, 8.1 prior to 8.1.21, 8.2 prior to 8.2.17, 8.3 prior to 8.3.11, 8.4 prior to 8.4.4, and 9.0 Beta before 9.0 Beta 2.

  • What type of attack can exploit CVE-2010-1170?

    CVE-2010-1170 can be exploited to load Tcl code from the pltcl_modules table, which could lead to remote code execution.

  • Is there a workaround for CVE-2010-1170 if I cannot upgrade?

    If upgrading is not an option, you can restrict access to the pltcl_modules table and ensure proper permission settings to mitigate the risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203