CVE-2009-4136

UnknownEPSS 3.64%

Last modified

CVE-2009-4136 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 3.64% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
3.64%

88.2th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
PostgresqlPostgresql7.4.1
PostgresqlPostgresql7.4.2
PostgresqlPostgresql7.4.3
PostgresqlPostgresql7.4.4
PostgresqlPostgresql7.4.5
PostgresqlPostgresql7.4.6
PostgresqlPostgresql7.4.7
PostgresqlPostgresql7.4.8
PostgresqlPostgresql7.4.9
PostgresqlPostgresql7.4.10
PostgresqlPostgresql7.4.11
PostgresqlPostgresql7.4.12
PostgresqlPostgresql7.4.13
PostgresqlPostgresql7.4.14
PostgresqlPostgresql7.4.15
PostgresqlPostgresql7.4.16
PostgresqlPostgresql7.4.17
PostgresqlPostgresql7.4.18
PostgresqlPostgresql7.4.19
PostgresqlPostgresql7.4.20
PostgresqlPostgresql7.4.21
PostgresqlPostgresql7.4.22
PostgresqlPostgresql7.4.23
PostgresqlPostgresql7.4.24
PostgresqlPostgresql7.4.25
PostgresqlPostgresql7.4.26
PostgresqlPostgresql8.0.0
PostgresqlPostgresql8.0.1
PostgresqlPostgresql8.0.2
PostgresqlPostgresql8.0.3
PostgresqlPostgresql8.0.4
PostgresqlPostgresql8.0.5
PostgresqlPostgresql8.0.6
PostgresqlPostgresql8.0.7
PostgresqlPostgresql8.0.8
PostgresqlPostgresql8.0.9
PostgresqlPostgresql8.0.10
PostgresqlPostgresql8.0.11
PostgresqlPostgresql8.0.12
PostgresqlPostgresql8.0.13
PostgresqlPostgresql8.0.14
PostgresqlPostgresql8.0.15
PostgresqlPostgresql8.0.16
PostgresqlPostgresql8.0.17
PostgresqlPostgresql8.0.18
PostgresqlPostgresql8.0.19
PostgresqlPostgresql8.0.20
PostgresqlPostgresql8.0.21
PostgresqlPostgresql8.0.22
PostgresqlPostgresql8.1.0

Showing 50 of 92 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

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?
Severity scoring for CVE-2009-4136 is pending analysis. The EPSS model estimates a 3.64% probability of exploitation in the next 30 days.
How do I fix CVE-2009-4136?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2009-4136?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST