CVE-2012-2143Not scoredCWE-310

CVE-2012-2143: Postgresql vulnerability

Postgresql

Fixed in 9.0-RELEASE-p2 · Affected: Postgresql before 9.0-RELEASE-p2 · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

5.7%probability of exploitation in the next 30 days

93rd percentile

050100

Higher than 93% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

The crypt_des (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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Cryptographic Issues · Cryptography
Vendor: Postgresql
Published: July 2012
Band: Possible (1 to 10%), July 2012

CoverageNo articles yet

No CyberSIXT article names CVE-2012-2143 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

13 more references are in the CVE record.