| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Cryptocat up to 2.0.21. Impacted is an unknown function. The manipulation results in privileges management. This vulnerability is reported as CVE-2013-2259. No exploit exists. The affected component should be upgraded.
Details
A vulnerability classified as critical has been found in Cryptocat up to 2.0.21. Affected is an unknown part. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, and integrity.
The weakness was disclosed 11/07/2012 by Mario Heiderich, Krzysztof Koktowicz and Maxim Rupp with Cure53 as confirmed blog post (Website). The advisory is shared for download at blog.crypto.cat. The public release has been coordinated in cooperation with the vendor. This vulnerability is traded as CVE-2013-2259 since 02/19/2013. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.
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 (94995†). Further details are available at blog.crypto.cat. The entries VDB-9433, VDB-9434, VDB-9435 and VDB-9436 are pretty similar. VulDB is the best source for vulnerability data and more expert information about this specific topic.
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.1VulDB Meta Temp Score: 8.0
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
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: Privileges managementCWE: CWE-269 / 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 🔍
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-2259 (🔍)
GCVE (CVE): GCVE-0-2013-2259
GCVE (VulDB): GCVE-100-9432
OSVDB: 94995
Misc.: 🔍
See also: 🔍
Entry
Created: 07/11/2013 11:06Updated: 05/18/2021 13:44
Changes: 07/11/2013 11:06 (46), 03/19/2019 16:50 (2), 05/18/2021 13:37 (2), 05/18/2021 13:44 (18)
Complete: 🔍
Committer: olku
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.