| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Cryptocat up to 2.0.21. This affects the function Cryptocat.random. Performing a manipulation results in an unknown weakness.
This vulnerability is known as CVE-2013-2260. No exploit is available.
It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Cryptocat up to 2.0.21. 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. The impact remains unknown.
The weakness was published 11/07/2012 by Mario Heiderich, Krzysztof Koktowicz and Maxim Rupp with Cure53 as confirmed blog post (Website). It is possible to read the advisory at blog.crypto.cat. The public release has been coordinated with the project team. This vulnerability is uniquely identified as CVE-2013-2260 since 02/19/2013. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.
Upgrading to version 2.0.22 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (94998†). Further details are available at blog.crypto.cat. Similar entries are available at VDB-9432, VDB-9433, VDB-9434 and VDB-9436. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 2.0.0
- 2.0.1
- 2.0.2
- 2.0.3
- 2.0.4
- 2.0.5
- 2.0.6
- 2.0.7
- 2.0.8
- 2.0.9
- 2.0.10
- 2.0.11
- 2.0.12
- 2.0.13
- 2.0.14
- 2.0.15
- 2.0.16
- 2.0.17
- 2.0.18
- 2.0.19
- 2.0.20
- 2.0.21
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: EntropyCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Cryptocat 2.0.22
Timeline
11/07/2012 🔍11/07/2012 🔍
02/19/2013 🔍
07/11/2013 🔍
05/18/2021 🔍
Sources
Advisory: blog.crypto.catResearcher: Mario Heiderich, Krzysztof Koktowicz, Maxim Rupp
Organization: Cure53
Status: Confirmed
Coordinated: 🔍
CVE: CVE-2013-2260 (🔍)
GCVE (CVE): GCVE-0-2013-2260
GCVE (VulDB): GCVE-100-9435
OSVDB: 94998
Misc.: 🔍
See also: 🔍
Entry
Created: 07/11/2013 11:23Updated: 05/18/2021 14:12
Changes: 07/11/2013 11:23 (46), 03/19/2019 16:41 (1), 05/18/2021 14:08 (2), 05/18/2021 14:12 (20)
Complete: 🔍
Committer: olku
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.