LibreSSL 2.0.0/2.0.1 PRNG missing encryption

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.
3.5$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in LibreSSL 2.0.0/2.0.1. This impacts an unknown function of the component PRNG. Performing a manipulation results in missing encryption. This vulnerability is reported as CVE-2014-2970. No exploit exists. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability, which was classified as problematic, was found in LibreSSL 2.0.0/2.0.1. This affects an unknown code of the component PRNG. The manipulation with an unknown input leads to a missing encryption vulnerability. CWE is classifying the issue as CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. This is going to have an impact on integrity.

The weakness was disclosed 07/16/2014 as confirmed mailinglist post (oss-sec). The advisory is shared at seclists.org. This vulnerability is uniquely identified as CVE-2014-2970 since 04/21/2014. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 for this issue.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at opensslrampage.org. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (94640) and SecurityFocus (BID 68667†). Further details are available at agwa.name. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.0
VulDB Meta Temp Score: 3.5

VulDB Base Score: 4.0
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Missing encryption
CWE: CWE-311 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Unproven
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: opensslrampage.org

Timelineinfo

04/21/2014 🔍
07/15/2014 +85 days 🔍
07/16/2014 +1 days 🔍
07/16/2014 +0 days 🔍
07/20/2014 +4 days 🔍
07/31/2014 +11 days 🔍
04/12/2019 +1716 days 🔍

Sourcesinfo

Advisory: seclists.org
Status: Confirmed

CVE: CVE-2014-2970 (🔍)
GCVE (CVE): GCVE-0-2014-2970
GCVE (VulDB): GCVE-100-67197
X-Force: 94640 - LibreSSL PRNG weak security, Low Risk
SecurityFocus: 68667 - RETIRED: LibreSSL PRNG Entropy Weakness

Misc.: 🔍

Entryinfo

Created: 07/20/2014 20:42
Updated: 04/12/2019 11:10
Changes: 07/20/2014 20:42 (53), 04/12/2019 11:10 (1)
Complete: 🔍
Cache ID: 216:B9E: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.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!