CVE-2009-4136
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
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Postgresql | Postgresql | 7.4.1 |
| Postgresql | Postgresql | 7.4.2 |
| Postgresql | Postgresql | 7.4.3 |
| Postgresql | Postgresql | 7.4.4 |
| Postgresql | Postgresql | 7.4.5 |
| Postgresql | Postgresql | 7.4.6 |
| Postgresql | Postgresql | 7.4.7 |
| Postgresql | Postgresql | 7.4.8 |
| Postgresql | Postgresql | 7.4.9 |
| Postgresql | Postgresql | 7.4.10 |
| Postgresql | Postgresql | 7.4.11 |
| Postgresql | Postgresql | 7.4.12 |
| Postgresql | Postgresql | 7.4.13 |
| Postgresql | Postgresql | 7.4.14 |
| Postgresql | Postgresql | 7.4.15 |
| Postgresql | Postgresql | 7.4.16 |
| Postgresql | Postgresql | 7.4.17 |
| Postgresql | Postgresql | 7.4.18 |
| Postgresql | Postgresql | 7.4.19 |
| Postgresql | Postgresql | 7.4.20 |
| Postgresql | Postgresql | 7.4.21 |
| Postgresql | Postgresql | 7.4.22 |
| Postgresql | Postgresql | 7.4.23 |
| Postgresql | Postgresql | 7.4.24 |
| Postgresql | Postgresql | 7.4.25 |
| Postgresql | Postgresql | 7.4.26 |
| Postgresql | Postgresql | 8.0.0 |
| Postgresql | Postgresql | 8.0.1 |
| Postgresql | Postgresql | 8.0.2 |
| Postgresql | Postgresql | 8.0.3 |
| Postgresql | Postgresql | 8.0.4 |
| Postgresql | Postgresql | 8.0.5 |
| Postgresql | Postgresql | 8.0.6 |
| Postgresql | Postgresql | 8.0.7 |
| Postgresql | Postgresql | 8.0.8 |
| Postgresql | Postgresql | 8.0.9 |
| Postgresql | Postgresql | 8.0.10 |
| Postgresql | Postgresql | 8.0.11 |
| Postgresql | Postgresql | 8.0.12 |
| Postgresql | Postgresql | 8.0.13 |
| Postgresql | Postgresql | 8.0.14 |
| Postgresql | Postgresql | 8.0.15 |
| Postgresql | Postgresql | 8.0.16 |
| Postgresql | Postgresql | 8.0.17 |
| Postgresql | Postgresql | 8.0.18 |
| Postgresql | Postgresql | 8.0.19 |
| Postgresql | Postgresql | 8.0.20 |
| Postgresql | Postgresql | 8.0.21 |
| Postgresql | Postgresql | 8.0.22 |
| Postgresql | Postgresql | 8.1.0 |
Showing 50 of 92 affected configurations. See NVD for the full list.
References
- http://www.postgresql.org/docs/current/static/release-7-4-27.htmlPatch, Vendor Advisory
- http://www.postgresql.org/docs/current/static/release-8-0-23.htmlPatch, Vendor Advisory
- http://www.postgresql.org/docs/current/static/release-8-1-19.htmlPatch, Vendor Advisory
- http://www.postgresql.org/docs/current/static/release-8-2-15.htmlPatch, Vendor Advisory
- http://www.postgresql.org/docs/current/static/release-8-3-9.htmlPatch, Vendor Advisory
- http://www.postgresql.org/docs/current/static/release-8-4-2.htmlPatch, Vendor Advisory
- http://www.postgresql.org/support/security.htmlVendor Advisory
- http://www.postgresql.org/docs/current/static/release-7-4-27.htmlPatch, Vendor Advisory
- http://www.postgresql.org/docs/current/static/release-8-0-23.htmlPatch, Vendor Advisory
- http://www.postgresql.org/docs/current/static/release-8-1-19.htmlPatch, Vendor Advisory
- http://www.postgresql.org/docs/current/static/release-8-2-15.htmlPatch, Vendor Advisory
- http://www.postgresql.org/docs/current/static/release-8-3-9.htmlPatch, Vendor Advisory
- http://www.postgresql.org/docs/current/static/release-8-4-2.htmlPatch, Vendor Advisory
- http://www.postgresql.org/support/security.htmlVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2009-4136?
How severe is CVE-2009-4136?
How do I fix CVE-2009-4136?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2009
- CVE-2009-4130Visual truncation vulnerability in the MakeScriptDialogTitle…
- CVE-2009-4131The EXT4_IOC_MOVE_EXT (aka move extents) ioctl implementatio…
- CVE-2009-4132Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2009-4133Condor 6.5.4 through 7.2.4, 7.3.x, and 7.4.0, as used in MRG…
- CVE-2009-4134Buffer underflow in the rgbimg module in Python 2.5 allows r…
- CVE-2009-4135The distcheck rule in dist-check.mk in GNU coreutils 5.2.1 t…
- CVE-2009-4137The loadContentFromCookie function in core/Cookie.php in Piw…
- CVE-2009-4138drivers/firewire/ohci.c in the Linux kernel before 2.6.32-gi…
- CVE-2009-4139A flaw was found in Spacewalk Java site packages. This cross…6.8
- CVE-2009-4140Unrestricted file upload vulnerability in ofc_upload_image.p…
- CVE-2009-4141Use-after-free vulnerability in the fasync_helper function i…
- CVE-2009-4142The htmlspecialchars function in PHP before 5.2.12 does not …
Are you affected by CVE-2009-4136?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST