Cryptocat up to 2.0.21 Multiparty Encryption information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Cryptocat up to 2.0.21. The impacted element is an unknown function of the component Multiparty Encryption. Such manipulation leads to information disclosure. This vulnerability is traded as CVE-2013-4105. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, has been found in Cryptocat up to 2.0.21. Affected by this issue is an unknown code block of the component Multiparty Encryption. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality.
The weakness was shared 11/07/2012 by Mario Heiderich, Krzysztof Koktowicz and Maxim Rupp with Cure53 as confirmed blog post (Website). The advisory is available at blog.crypto.cat. The vendor cooperated in the coordination of the public release. This vulnerability is handled as CVE-2013-4105 since 06/12/2013. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
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 (94997†). blog.crypto.cat is providing further details. The entries VDB-9432, VDB-9433, VDB-9435 and VDB-9436 are related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.
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: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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 🔍
06/12/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-4105 (🔍)
GCVE (CVE): GCVE-0-2013-4105
GCVE (VulDB): GCVE-100-9434
OSVDB: 94997
Misc.: 🔍
See also: 🔍
Entry
Created: 07/11/2013 11:18Updated: 05/18/2021 14:06
Changes: 07/11/2013 11:18 (47), 03/19/2019 16:46 (1), 05/18/2021 14:01 (2), 05/18/2021 14:06 (19)
Complete: 🔍
Committer: olku
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.