CVE-2009-4136

CVE-2009-4136 is a medium-severity vulnerability in Postgresql with a CVSS 2.0 base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

• Severity: Medium (CVSS 2.0 base score 6.5)
• EPSS exploit prediction: 4% (88th percentile)
• Actively exploited: Not listed in CISA KEV
• Affected product: Postgresql
• Published: 2009-12-15
• Last modified: 2026-06-16

Description

PostgreSQL 7.4.x before 7.4.27, 8.0.x before 8.0.23, 8.1.x before 8.1.19, 8.2.x before 8.2.15, 8.3.x before 8.3.9, and 8.4.x before 8.4.2 does not properly manage session-local state during execution of an index function by a database superuser, which allows remote authenticated users to gain privileges via a table with crafted index functions, as demonstrated by functions that modify (1) search_path or (2) a prepared statement, a related issue to CVE-2007-6600 and CVE-2009-3230.

Frequently asked questions

What is CVE-2009-4136?

PostgreSQL 7.4.x before 7.4.27, 8.0.x before 8.0.23, 8.1.x before 8.1.19, 8.2.x before 8.2.15, 8.3.x before 8.3.9, and 8.4.x before 8.4.2 does not properly manage session-local state during execution of an index function by a database superuser, which allows remote authenticated users to gain privileges via a table with crafted index functions, as demonstrated by functions that modify (1) search_path or (2) a prepared statement, a related issue to CVE-2007-6600 and CVE-2009-3230.

How severe is CVE-2009-4136?

CVE-2009-4136 has a CVSS 2.0 base score of 6.5, rated medium severity.

Is CVE-2009-4136 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (88th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2009-4136?

CVE-2009-4136 primarily affects Postgresql. In total, 92 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2009-4136?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2009-4136 published?

CVE-2009-4136 was published on 2009-12-15 and last updated on 2026-06-16.

References

• http://lists.opensuse.org/opensuse-security-announce/2010-01/msg00007.html
• http://marc.info/?l=bugtraq&m=134124585221119&w=2
• http://osvdb.org/61039
• http://secunia.com/advisories/37663
• http://secunia.com/advisories/39820
• http://wiki.rpath.com/wiki/Advisories:rPSA-2010-0012
• http://www.mandriva.com/security/advisories?name=MDVSA-2009:333
• http://www.postgresql.org/docs/current/static/release-7-4-27.html
• http://www.postgresql.org/docs/current/static/release-8-0-23.html
• http://www.postgresql.org/docs/current/static/release-8-1-19.html
• http://www.postgresql.org/docs/current/static/release-8-2-15.html
• http://www.postgresql.org/docs/current/static/release-8-3-9.html
• http://www.postgresql.org/docs/current/static/release-8-4-2.html
• http://www.postgresql.org/support/security.html
• http://www.redhat.com/support/errata/RHSA-2010-0427.html
• http://www.redhat.com/support/errata/RHSA-2010-0428.html
• http://www.redhat.com/support/errata/RHSA-2010-0429.html
• http://www.securityfocus.com/archive/1/509917/100/0/threaded
• http://www.securityfocus.com/bid/37333
• http://www.securitytracker.com/id?1023326
• http://www.vupen.com/english/advisories/2009/3519
• http://www.vupen.com/english/advisories/2010/1197
• https://bugzilla.redhat.com/show_bug.cgi?id=546321
• https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9358
• https://www.redhat.com/archives/fedora-package-announce/2009-December/msg01035.html
• https://www.redhat.com/archives/fedora-package-announce/2009-December/msg01056.html

Affected products (92)

• cpe:2.3:a:postgresql:postgresql:7.4.1:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.2:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.3:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.4:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.5:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.6:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.7:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.8:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.9:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.10:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.11:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.12:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.13:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.14:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.15:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.16:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.17:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.18:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.19:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.20:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.21:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.22:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.23:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.24:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.25:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:7.4.26:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.0:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.1:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.2:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.3:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.4:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.5:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.6:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.7:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.8:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.9:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.10:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.11:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.12:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:8.0.13:*:*:*:*:*:*:*

More vulnerabilities in Postgresql

• CVE-2013-1903 — Critical (CVSS 10.0): PostgreSQL, possibly 9.2.x before 9.2.4, 9.1.x before 9.1.9, 9.0.x before 9.0.13, 8.4.x before 8.4.17, and 8.3.x before…
• CVE-2013-1902 — Critical (CVSS 10.0): PostgreSQL, 9.2.x before 9.2.4, 9.1.x before 9.1.9, 9.0.x before 9.0.13, 8.4.x before 8.4.17, and 8.3.x before 8.3.23…
• CVE-2007-3279 — Critical (CVSS 10.0): PostgreSQL 8.1 and probably later versions, when the PL/pgSQL (plpgsql) language has been created, grants certain…
• CVE-2002-1399 — Critical (CVSS 10.0): Unknown vulnerability in cash_out and possibly other functions in PostgreSQL 7.2.1 and earlier, and possibly later…
• CVE-2015-0244 — Critical (CVSS 9.8): PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 does not…
• CVE-2015-3166 — Critical (CVSS 9.8): The snprintf implementation in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7,…

All CVEs affecting Postgresql →