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 do
Noroxi assessment
Priority: Monitor (action score 24/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.1% (FIRST EPSS); higher than 81.7% of all records.
- Fixed version: postgresql-7.4 (Debian:4.0) 1:7.4.27-0etch1; postgresql-8.1 (Debian:4.0) 8.1.19-0etch1; postgresql-8.3 (Debian:5.0) 8.3.9-0lenny1.
Low priority for now. Upgrade to postgresql-7.4 (Debian:4.0) 1:7.4.27-0etch1; postgresql-8.1 (Debian:4.0) 8.1.19-0etch1; postgresql-8.3 (Debian:5.0) 8.3.9-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
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 handle a '\0' character in a domain name in the subject's Common Name (CN) field of an X.509 certificate, which (1) allows man-in-the-middle attackers to spoof arbitrary SSL-based PostgreSQL servers via a crafted server certificate issued by a legitimate Certification Authority, and (2) allows remote attackers to bypass intended client-hostname restrictions via a crafted client certificate issued by a legitimate Certification Authority, a related issue to CVE-2009-2408.
- Published
- Dec 15, 2009
- Updated
- Jun 16, 2026
- EPSS
- 2.1% · 81th percentile
- CWE
- CWE-310
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.1%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.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
- 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.26
- 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.27-0etch1 | 1:7.4.27-0etch1 |
| Debian:4.0 | postgresql-8.1 | before 8.1.19-0etch1 | 8.1.19-0etch1 |
| Debian:5.0 | postgresql-8.3 | before 8.3.9-0lenny1 | 8.3.9-0lenny1 |
| openSUSE:Tumbleweed | postgresql93 | before 9.3.15-1.1 | 9.3.15-1.1 |
| openSUSE:Tumbleweed | postgresql94 | before 9.4.10-1.1 | 9.4.10-1.1 |
| openSUSE:Tumbleweed | postgresql95 | before 9.5.4-1.2 | 9.5.4-1.2 |
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 attackers57Plan
- 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-3230Sep 17, 2009 · 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.427Monitor
- ← EarlierCVE-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
- Later →CVE-2009-4136Dec 15, 2009 · 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 do27Monitor
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.27-0etch1 · Debian:4.0 | Package registry (OSV) |
| debian:postgresql-8.1 | 8.1.19-0etch1 · Debian:4.0 | Package registry (OSV) |
| debian:postgresql-8.3 | 8.3.9-0lenny1 · Debian:5.0 | Package registry (OSV) |
| opensuse:postgresql93 | 9.3.15-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql94 | 9.4.10-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:postgresql95 | 9.5.4-1.2 · openSUSE:Tumbleweed | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
If successful
- Confidentiality
- none
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- None
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-310 · Cryptographic IssuesCVSS vector
AV:N/AC:M/Au:N/C:N/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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (18 more)Show less
- marc.info/?l=bugtraq&m=134124585221119&w=2
- osvdb.org/61038
- secunia.com/advisories/37663
- wiki.rpath.com/wiki/Advisories:rPSA-2010-0012
- www.mandriva.com/security/advisories?name=MDVSA-2009:333
- www.postgresql.org/docs/current/static/release-7-4-27.html
- www.postgresql.org/docs/current/static/release-8-0-23.html
- www.postgresql.org/docs/current/static/release-8-1-19.html
- www.postgresql.org/docs/current/static/release-8-2-15.html
- www.postgresql.org/docs/current/static/release-8-3-9.html
- www.postgresql.org/docs/current/static/release-8-4-2.html
- www.postgresql.org/support/security.html
- www.securityfocus.com/archive/1/509917/100/0/threaded
- www.securityfocus.com/bid/37334
- www.securitytracker.com/id?1023325
- www.vupen.com/english/advisories/2009/3519
- www.redhat.com/archives/fedora-package-announce/2009-December/msg01035.html
- www.redhat.com/archives/fedora-package-announce/2009-December/msg01056.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.