CVE-2009-3230: The core server component in PostgreSQL 8.4 before 8.4.1, 8.3 before 8.3.8, 8.2 before 8.2.14, 8.1 before 8.1.18, 8.0 before 8.0.22, and 7.4…
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.8% (FIRST EPSS); higher than 86.8% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: postgresql-7.4 (Debian:4.0) 1:7.4.26-0etch1; postgresql-8.1 (Debian:4.0) 8.1.18-0etch1; postgresql-8.3 (Debian:5.0) 8.3.8-0lenny1.
Low priority for now. Upgrade to postgresql-7.4 (Debian:4.0) 1:7.4.26-0etch1; postgresql-8.1 (Debian:4.0) 8.1.18-0etch1; postgresql-8.3 (Debian:5.0) 8.3.8-0lenny1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The core server component in PostgreSQL 8.4 before 8.4.1, 8.3 before 8.3.8, 8.2 before 8.2.14, 8.1 before 8.1.18, 8.0 before 8.0.22, and 7.4 before 7.4.26 does not use the appropriate privileges for the (1) RESET ROLE and (2) RESET SESSION AUTHORIZATION operations, which allows remote authenticated users to gain privileges. NOTE: this is due to an incomplete fix for CVE-2007-6600.
- Published
- Sep 17, 2009
- Updated
- Jun 16, 2026
- EPSS
- 2.8% · 86th percentile
- CWE
- CWE-264
Report tools
Action score
27
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.8%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is PostgreSQL on your server exposed to the internet?Run a port scan
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| postgresql | postgresql | cpe:2.3:a:postgresql:postgresql |
Using postgresql? Add it to your stack and be the first to know about CVEs like this one. (PostgreSQL)
Is PostgreSQL on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- postgresql postgresql7.4
- postgresql postgresql7.4.1
- postgresql postgresql7.4.10
- postgresql postgresql7.4.11
- postgresql postgresql7.4.12
- postgresql postgresql7.4.13
- postgresql postgresql7.4.14
- postgresql postgresql7.4.15
+12 more rows
- postgresql postgresql7.4.16
- postgresql postgresql7.4.17
- postgresql postgresql7.4.18
- postgresql postgresql7.4.19
- postgresql postgresql7.4.2
- postgresql postgresql7.4.20
- postgresql postgresql7.4.21
- postgresql postgresql7.4.22
- postgresql postgresql7.4.23
- postgresql postgresql7.4.24
- postgresql postgresql7.4.25
- postgresql postgresql7.4.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:4.0 | postgresql-7.4 | before 1:7.4.26-0etch1 | 1:7.4.26-0etch1 |
| Debian:4.0 | postgresql-8.1 | before 8.1.18-0etch1 | 8.1.18-0etch1 |
| Debian:5.0 | postgresql-8.3 | before 8.3.8-0lenny1 | 8.3.8-0lenny1 |
| Red Hat:enterprise_linux:3::as | rh-postgresql | before 0:7.3.21-2 | 0:7.3.21-2 |
| Red Hat:enterprise_linux:3::as | rh-postgresql-contrib | before 0:7.3.21-2 | 0:7.3.21-2 |
| Red Hat:enterprise_linux:3::as | rh-postgresql-debuginfo | before 0:7.3.21-2 | 0:7.3.21-2 |
| Red Hat:enterprise_linux:3::as | rh-postgresql-devel | before 0:7.3.21-2 | 0:7.3.21-2 |
| Red Hat:enterprise_linux:3::as | rh-postgresql-docs | before 0:7.3.21-2 | 0:7.3.21-2 |
| Red Hat:enterprise_linux:3::as | rh-postgresql-jdbc | before 0:7.3.21-2 | 0:7.3.21-2 |
| Red Hat:enterprise_linux:3::as | rh-postgresql-libs | before 0:7.3.21-2 | 0:7.3.21-2 |
| Red Hat:enterprise_linux:3::as | rh-postgresql-pl | before 0:7.3.21-2 | 0:7.3.21-2 |
| Red Hat:enterprise_linux:3::as | rh-postgresql-python | before 0:7.3.21-2 | 0:7.3.21-2 |
| Red Hat:enterprise_linux:3::as | rh-postgresql-server | before 0:7.3.21-2 | 0:7.3.21-2 |
| Red Hat:enterprise_linux:3::as | rh-postgresql-tcl | before 0:7.3.21-2 | 0:7.3.21-2 |
| Red Hat:enterprise_linux:3::as | rh-postgresql-test | before 0:7.3.21-2 | 0:7.3.21-2 |
| Red Hat:enterprise_linux:4::as | postgresql | before 0:7.4.26-1.el4_8.1 | 0:7.4.26-1.el4_8.1 |
| Red Hat:enterprise_linux:4::as | postgresql-contrib | before 0:7.4.26-1.el4_8.1 | 0:7.4.26-1.el4_8.1 |
| Red Hat:enterprise_linux:4::as | postgresql-debuginfo | before 0:7.4.26-1.el4_8.1 | 0:7.4.26-1.el4_8.1 |
| Red Hat:enterprise_linux:4::as | postgresql-devel | before 0:7.4.26-1.el4_8.1 | 0:7.4.26-1.el4_8.1 |
| Red Hat:enterprise_linux:4::as | postgresql-docs | before 0:7.4.26-1.el4_8.1 | 0:7.4.26-1.el4_8.1 |
| Red Hat:enterprise_linux:4::as | postgresql-jdbc | before 0:7.4.26-1.el4_8.1 | 0:7.4.26-1.el4_8.1 |
| Red Hat:enterprise_linux:4::as | postgresql-libs | before 0:7.4.26-1.el4_8.1 | 0:7.4.26-1.el4_8.1 |
| Red Hat:enterprise_linux:4::as | postgresql-pl | before 0:7.4.26-1.el4_8.1 | 0:7.4.26-1.el4_8.1 |
| Red Hat:enterprise_linux:4::as | postgresql-python | before 0:7.4.26-1.el4_8.1 | 0:7.4.26-1.el4_8.1 |
+67
Same product
postgresql: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-7546PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allowing remote…57Plan
- CVE-2019-9193In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' group to…55Plan
- CVE-2020-25695A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24.49Plan
Published before and after this one in the same product
- ← EarlierCVE-2009-0922Mar 17, 2009 · PostgreSQL before 8.3.7, 8.2.13, 8.1.17, 8.0.21, and 7.4.25 allows remote authenticated users to cause a denial of service (stack…19Monitor
- ← EarlierCVE-2009-3229Sep 17, 2009 · The core server component in PostgreSQL 8.4 before 8.4.1, 8.3 before 8.3.8, and 8.2 before 8.2.14 allows remote authenticated users to…17Monitor
- Later →CVE-2009-3231Sep 17, 2009 · The core server component in PostgreSQL 8.3 before 8.3.8 and 8.2 before 8.2.14, when using LDAP authentication with anonymous binds, allows…29Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:postgresql-7.4 | 1:7.4.26-0etch1 · Debian:4.0 | Package registry (OSV) |
| debian:postgresql-8.1 | 8.1.18-0etch1 · Debian:4.0 | Package registry (OSV) |
| debian:postgresql-8.3 | 8.3.8-0lenny1 · Debian:5.0 | Package registry (OSV) |
| red hat:httpd | 0:2.2.13-2.el5s2 · Red Hat:rhel_application_stack:2 | Package registry (OSV) |
| red hat:httpd-debuginfo | 0:2.2.13-2.el5s2 · Red Hat:rhel_application_stack:2 | Package registry (OSV) |
| red hat:httpd-devel | 0:2.2.13-2.el5s2 · Red Hat:rhel_application_stack:2 | Package registry (OSV) |
| red hat:httpd-manual | 0:2.2.13-2.el5s2 · Red Hat:rhel_application_stack:2 | Package registry (OSV) |
| red hat:mod_ssl | 1:2.2.13-2.el5s2 · Red Hat:rhel_application_stack:2 | Package registry (OSV) |
| red hat:mysql | 0:5.0.84-2.el5s2 · Red Hat:rhel_application_stack:2 | Package registry (OSV) |
| red hat:mysql-bench | 0:5.0.84-2.el5s2 · Red Hat:rhel_application_stack:2 | Package registry (OSV) |
| red hat:mysql-cluster | 0:5.0.84-2.el5s2 · Red Hat:rhel_application_stack:2 | Package registry (OSV) |
| red hat:mysql-debuginfo | 0:5.0.84-2.el5s2 · Red Hat:rhel_application_stack:2 | Package registry (OSV) |
| red hat:mysql-devel | 0:5.0.84-2.el5s2 · Red Hat:rhel_application_stack:2 | Package registry (OSV) |
| red hat:mysql-libs | 0:5.0.84-2.el5s2 · Red Hat:rhel_application_stack:2 | Package registry (OSV) |
| red hat:mysql-server | 0:5.0.84-2.el5s2 · Red Hat:rhel_application_stack:2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
AV:N/AC:L/Au:S/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- lists.opensuse.org/opensuse-security-announce/2009-10/msg00001.html
- lists.opensuse.org/opensuse-security-announce/2009-10/msg00004.html
- marc.info/?l=bugtraq&m=134124585221119&w=2
- secunia.com/advisories/36660
- secunia.com/advisories/36695
- secunia.com/advisories/36727
- secunia.com/advisories/36800
- secunia.com/advisories/36837
- sunsolve.sun.com/search/document.do?assetkey=1-66-270408-1
- wiki.rpath.com/wiki/Advisories:rPSA-2010-0012
- www.postgresql.org/docs/8.3/static/release-8-3-8.html
- www.postgresql.org/support/security.html
- www.securityfocus.com/archive/1/509917/100/0/threaded
- www.securityfocus.com/bid/36314
- www.ubuntu.com/usn/usn-834-1
- www.us.debian.org/security/2009/dsa-1900
- www.vupen.com/english/advisories/2009/2602
- bugzilla.redhat.com/show_bug.cgi?id=522085
- oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10166
Vendor advisories and official records. Exploit/PoC links are deliberately left out.