CVE-2009-4034 json
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 d…
published 16y ago modified 4mo ago also EUVD-2009-4005
- cvss
- 5.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- postgresql94 openSUSE Tumbleweed 9.4.10-1.1
- postgresql93 openSUSE Tumbleweed 9.3.15-1.1
- postgresql95 openSUSE Tumbleweed 9.5.4-1.2
opensuse advisories openSUSE-SU-2024:10030-1openSUSE-SU-2024:10256-1openSUSE-SU-2024:10273-1
- postgresql.org/docs/current/static/release-8-2-15.html advisory
- postgresql.org/docs/current/static/release-8-4-2.html advisory
- postgresql.org/docs/current/static/release-8-0-23.html advisory
- postgresql.org/docs/current/static/release-8-3-9.html advisory
- postgresql.org/docs/current/static/release-7-4-27.html advisory
- postgresql.org/docs/current/static/release-8-1-19.html advisory
Is CVE-2009-4034 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2009-4034 updated cvss 3.6
postgresql: incorrect verification of SSL certificates with NUL in name
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.13% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-14).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:N/I:P/A:P |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
- Technology feeds
References
-
postgresql.org
/docs/current/static/release-8-2-15.html
patch, vendor-advisory
-
postgresql.org
/docs/current/static/release-8-4-2.html
patch, vendor-advisory
-
postgresql.org
/docs/current/static/release-8-0-23.html
patch, vendor-advisory
-
postgresql.org
/docs/current/static/release-8-3-9.html
patch, vendor-advisory
-
postgresql.org
/docs/current/static/release-7-4-27.html
patch, vendor-advisory
-
postgresql.org
/docs/current/static/release-8-1-19.html
patch, vendor-advisory
-
marc.info
/?l=bugtraq&m=134124585221119&w=2
vendor-advisory
-
redhat.com
/archives/fedora-package-announce/2009-December/msg01035.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2010-01/msg00007.html
vendor-advisory
-
redhat.com
/archives/fedora-package-announce/2009-December/msg01056.html
vendor-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2009:333
vendor-advisory
-
postgresql.org
/support/security.html
vendor-advisory
-
osvdb.org
/61038
vdb-entry
-
securityfocus.com
/archive/1/509917/100/0/threaded
mailing-list
-
securitytracker.com
/id?1023325
vdb-entry
-
securityfocus.com
/bid/37334
vdb-entry
-
vupen.com
/english/advisories/2009/3519
vdb-entry
-
secunia.com
/advisories/37663
third-party-advisory
- wiki.rpath.com /wiki/Advisories:rPSA-2010-0012
Sources
- CVE List CVE-2009-4034
- NVD CVE-2009-4034
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.