CVE-2009-4034: Medium severity postgresql common vulnerability
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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2009-4034?
CVE-2009-4034 is classified as a high severity vulnerability due to its potential to allow man-in-the-middle attacks.
How do I fix CVE-2009-4034?
To mitigate CVE-2009-4034, upgrade to PostgreSQL version 7.4.27, 8.0.23, 8.1.19, 8.2.15, 8.3.9, or 8.4.2 or later.
Which versions of PostgreSQL are affected by CVE-2009-4034?
CVE-2009-4034 affects PostgreSQL versions 7.4.x (up to 7.4.26), 8.0.x (up to 8.0.22), 8.1.x (up to 8.1.18), 8.2.x (up to 8.2.14), 8.3.x (up to 8.3.8), and 8.4.x (up to 8.4.1).
What is the potential impact of CVE-2009-4034?
The vulnerability could allow attackers to perform man-in-the-middle attacks by exploiting improper handling of the '\0' character in domain names.
Is there a workaround for CVE-2009-4034?
While the best solution is to upgrade, implementing strict validation of X.509 certificates may serve as a temporary workaround for CVE-2009-4034.