| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Cryptocat up to 2.0.21. This impacts an unknown function. Performing a manipulation results in input validation. This vulnerability was named CVE-2013-4103. The attack may be initiated remotely. In addition, an exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Cryptocat up to 2.0.21. This affects an unknown code. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Cryptocat before 2.1.12 has Remote Script Injection due to improperly sanitizing user input
The bug was discovered 11/06/2015. The weakness was presented 11/04/2019 by Maxim Rupp. This vulnerability is uniquely identified as CVE-2013-4103 since 06/12/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 unknown but a public exploit is available.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1459 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.0.22 eliminates this vulnerability.
The vulnerability is also documented in the databases at Exploit-DB (38637), SecurityFocus (BID 61093†) and OSVDB (95007†). See VDB-9444 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider 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: 8.5VulDB Meta Temp Score: 8.2
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
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: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Cryptocat 2.0.22
Timeline
11/07/2012 🔍06/12/2013 🔍
11/06/2015 🔍
11/04/2019 🔍
11/04/2019 🔍
12/21/2024 🔍
Sources
Advisory: 134252Researcher: Maxim Rupp
Status: Confirmed
CVE: CVE-2013-4103 (🔍)
GCVE (CVE): GCVE-0-2013-4103
GCVE (VulDB): GCVE-100-144813
SecurityFocus: 61093 - Cryptocat CVE-2013-4103 Arbitrary Script Injection Vulnerability
OSVDB: 95007
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 11/04/2019 19:20Updated: 12/21/2024 11:21
Changes: 11/04/2019 19:20 (40), 11/04/2019 19:25 (21), 02/01/2024 18:40 (5), 12/21/2024 11:21 (24)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.