Codeaurora Android-msm up to 3.16.1 Encryption debug log file
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Codeaurora Android-msm up to 3.16.1. This impacts an unknown function of the component Encryption. This manipulation causes debug log file. This vulnerability appears as CVE-2013-2599. There is no available exploit.
Details
A vulnerability was found in Codeaurora Android-msm up to 3.16.1. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component Encryption. The manipulation with an unknown input leads to a debug log file vulnerability. The CWE definition for the vulnerability is CWE-534. This entry has been deprecated because its abstraction was too low-level. See CWE-532. As an impact it is known to affect confidentiality. The summary by CVE is:
A certain Qualcomm Innovation Center (QuIC) patch to the NativeDaemonConnector class in services/java/com/android/server/NativeDaemonConnector.java in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.3.x enables debug logging, which allows attackers to obtain sensitive disk-encryption passwords via a logcat call.
The weakness was presented 08/31/2014 (Website). It is possible to read the advisory at codeaurora.org. This vulnerability is known as CVE-2013-2599 since 03/15/2013. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-70784, VDB-70782, VDB-70781 and VDB-70780 for similar entries. Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Debug log fileCWE: CWE-534 / CWE-532 / CWE-200
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/15/2013 🔍08/31/2014 🔍
08/31/2014 🔍
03/26/2015 🔍
03/12/2019 🔍
Sources
Advisory: codeaurora.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2013-2599 (🔍)
GCVE (CVE): GCVE-0-2013-2599
GCVE (VulDB): GCVE-100-70783
See also: 🔍
Entry
Created: 03/26/2015 12:07Updated: 03/12/2019 08:50
Changes: 03/26/2015 12:07 (47), 03/12/2019 08:50 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.