VDB-144837 · CVE-2013-2260 · BID 61091

Cryptocat up to 2.0.21 Entropy Cryptocat.random entropy

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

Summaryinfo

A vulnerability was found in Cryptocat up to 2.0.21. It has been rated as critical. Affected by this vulnerability is the function Cryptocat.random of the component Entropy Handler. Performing a manipulation results in entropy. This vulnerability is reported as CVE-2013-2260. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical has been found in Cryptocat up to 2.0.21. This affects the function Cryptocat.random of the component Entropy Handler. The manipulation with an unknown input leads to a entropy vulnerability. CWE is classifying the issue as CWE-331. The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Cryptocat before 2.0.22: Cryptocat.random() Function Array Key has Entropy Weakness

The weakness was disclosed 11/04/2019. This vulnerability is uniquely identified as CVE-2013-2260 since 02/19/2013. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

Upgrading to version 2.0.22 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at OSVDB (94998†). The entry VDB-9435 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.5
VulDB Meta Temp Score: 8.4

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Entropy
CWE: CWE-331 / CWE-330 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Cryptocat 2.0.22

Timelineinfo

02/19/2013 🔍
11/04/2019 +2449 days 🔍
11/05/2019 +1 days 🔍
02/04/2024 +1552 days 🔍

Sourcesinfo

Advisory: tobtu.com
Status: Not defined

CVE: CVE-2013-2260 (🔍)
GCVE (CVE): GCVE-0-2013-2260
GCVE (VulDB): GCVE-100-144837
SecurityFocus: 61091
OSVDB: 94998

See also: 🔍

Entryinfo

Created: 11/05/2019 10:34
Updated: 02/04/2024 07:42
Changes: 11/05/2019 10:34 (40), 11/05/2019 10:39 (17), 02/04/2024 07:42 (5)
Complete: 🔍
Cache ID: 216::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!