CVE-2012-2143: Medium severity postgresql vulnerability
A security flaw was found in the way DES and extended DES based crypt() password encryption function performed encryption of certain keys, when the key to be encrypted was provided in the Unicode encoding (certain keys were truncated before being DES digested). When the resulting ciphertext for such a previously shortened key was used as a pattern in a password protected resource, intended to be matched against subsequently encrypted value of the password field, retrieved from the user authentication dialog, it could lead to authentication bypass.
Other sources
The cryptdes (aka DES-based crypt) function in FreeBSD before 9.0-RELEASE-p2, as used in PHP, PostgreSQL, and other products, does not process the complete cleartext password if this password contains a 0x80 character, which makes it easier for context-dependent attackers to obtain access via an authentication attempt with an initial substring of the intended password, as demonstrated by a Unicode password.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2012-2143?
CVE-2012-2143 has been classified as a high-severity vulnerability due to its potential to expose sensitive password information.
How do I fix CVE-2012-2143?
To fix CVE-2012-2143, upgrade to PostgreSQL version 9.1.4 or later, 9.0.8 or later, 8.4.12 or later, or 8.3.19 or later.
What software is affected by CVE-2012-2143?
CVE-2012-2143 affects multiple versions of PostgreSQL and FreeBSD operating systems.
Can CVE-2012-2143 be exploited remotely?
Yes, CVE-2012-2143 can potentially be exploited remotely if malicious actors have access to the password encryption function.
What impact does CVE-2012-2143 have on password security?
CVE-2012-2143 can lead to the disclosure of passwords through improper encryption, thus compromising the security of user accounts.