Cryptocat up to 2.0.41 Group Chat Private Key Generator multiparty.js missing encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Cryptocat up to 2.0.41. This affects an unknown function of the file cryptocatRandom.js/multiparty.js of the component Group Chat Private Key Generator. The manipulation leads to missing encryption. This vulnerability is uniquely identified as CVE-2013-2257. Moreover, an exploit is present. You should upgrade the affected component.
Details
A vulnerability was found in Cryptocat up to 2.0.41 and classified as critical. This issue affects some unknown functionality of the file cryptocatRandom.js/multiparty.js of the component Group Chat Private Key Generator. The manipulation with an unknown input leads to a missing encryption vulnerability. Using CWE to declare the problem leads to CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. Impacted is confidentiality, and integrity.
The weakness was disclosed 04/19/2013 by Steve Thomas as confirmed blog post (Website). It is possible to read the advisory at tobtu.com. The public release has been coordinated in cooperation with the project team. The identification of this vulnerability is CVE-2013-2257 since 02/19/2013. 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. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.
After immediately, there has been an exploit disclosed. It is declared as proof-of-concept.
Upgrading to version 2.0.42 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (94855†). scmagazine.com is providing further details. The entry VDB-144834 is pretty similar. 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
- 2.0.22
- 2.0.23
- 2.0.24
- 2.0.25
- 2.0.26
- 2.0.27
- 2.0.28
- 2.0.29
- 2.0.30
- 2.0.31
- 2.0.32
- 2.0.33
- 2.0.34
- 2.0.35
- 2.0.36
- 2.0.37
- 2.0.38
- 2.0.39
- 2.0.40
- 2.0.41
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.0VulDB Meta Temp Score: 6.7
VulDB Base Score: 6.5
VulDB Temp Score: 5.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Missing encryptionCWE: CWE-311 / 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-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: 🔍
Exploit Delay Time: 🔍
Upgrade: Cryptocat 2.0.42
Patch: github.com
Timeline
02/19/2013 🔍04/19/2013 🔍
04/19/2013 🔍
04/19/2013 🔍
07/09/2013 🔍
05/18/2021 🔍
Sources
Product: github.comAdvisory: tobtu.com
Researcher: Steve Thomas
Status: Confirmed
Coordinated: 🔍
CVE: CVE-2013-2257 (🔍)
GCVE (CVE): GCVE-0-2013-2257
GCVE (VulDB): GCVE-100-9347
OSVDB: 94855
scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
See also: 🔍
Entry
Created: 07/09/2013 15:10Updated: 05/18/2021 07:33
Changes: 07/09/2013 15:10 (51), 03/19/2019 15:43 (2), 05/18/2021 07:27 (2), 05/18/2021 07:33 (18)
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.