FreeBSD up to 9.0 DES Implementation libcrypt Eingabe cryptographic issue

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.2$0-$5k0.00

Summaryinfo

A vulnerability has been found in FreeBSD up to 9.0 and classified as problematic. Affected is the function crypt in the library libcrypt of the component DES Implementation. The manipulation with the input bit set(0x80) as part of Eingabe leads to cryptographic issue. This vulnerability is uniquely identified as CVE-2012-2143. Moreover, an exploit is present. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in FreeBSD up to 9.0 (Operating System) and classified as critical. This issue affects the function crypt in the library libcrypt of the component DES Implementation. The manipulation with the input value bit set(0x80) leads to a cryptographic issue vulnerability. Using CWE to declare the problem leads to CWE-310. Impacted is confidentiality, and integrity. The summary by CVE is:

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.

The weakness was disclosed 05/30/2012 by Rubin Xu, Joseph Bonneau and Donting Yu as FreeBSD-SA-12:02.crypt as confirmed changelog entry (Website). The advisory is shared at security.freebsd.org. The identification of this vulnerability is CVE-2012-2143 since 04/04/2012. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1600 for this issue.

It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 74667 (openSUSE Security Update : php5 (openSUSE-SU-2012:0826-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 350652 (Amazon Linux Security Advisory for php: ALAS-2012-095).

Applying the patch r236304 is able to eliminate this problem. The bugfix is ready for download at git.php.net. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (74667), SecurityFocus (BID 53729†), OSVDB (82509†), Secunia (SA49342†) and SecurityTracker (ID 1026995†). The entries VDB-5481 and VDB-61220 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.1
VulDB Meta Temp Score: 8.2

VulDB Base Score: 9.1
VulDB Temp Score: 8.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Cryptographic issue
CWE: CWE-310
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 74667
Nessus Name: openSUSE Security Update : php5 (openSUSE-SU-2012:0826-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 71469
OpenVAS Name: Debian Security Advisory DSA 2491-1 (postgresql-8.4)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Patch: r236304

Timelineinfo

04/04/2012 🔍
04/30/2012 +26 days 🔍
05/30/2012 +30 days 🔍
05/30/2012 +0 days 🔍
05/30/2012 +0 days 🔍
05/31/2012 +1 days 🔍
06/05/2012 +5 days 🔍
06/06/2012 +1 days 🔍
07/05/2012 +29 days 🔍
06/13/2014 +708 days 🔍
04/28/2019 +1780 days 🔍

Sourcesinfo

Product: freebsd.org

Advisory: FreeBSD-SA-12:02.crypt
Researcher: Rubin Xu, Joseph Bonneau , Donting Yu
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2012-2143 (🔍)
GCVE (CVE): GCVE-0-2012-2143
GCVE (VulDB): GCVE-100-5477

OVAL: 🔍

SecurityFocus: 53729 - libcrypt 'crypt()' Password Encryption Weakness
Secunia: 49342 - Check Point IPSO DES Encryption Input Handling Weakness, Not Critical
OSVDB: 82509
SecurityTracker: 1026995

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 06/06/2012 15:24
Updated: 04/28/2019 06:38
Changes: 06/06/2012 15:24 (89), 04/28/2019 06:38 (1)
Complete: 🔍
Cache ID: 216:ABA:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!