| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Samsung 840 EVO. This affects an unknown part of the component Encryption Key. The manipulation leads to key management. This vulnerability is traded as CVE-2018-12038. It is possible to launch the attack on the physical device. There is no exploit available.
Details
A vulnerability, which was classified as problematic, has been found in Samsung 840 EVO (the affected version is unknown). This issue affects an unknown code of the component Encryption Key. The manipulation with an unknown input leads to a key management vulnerability. Using CWE to declare the problem leads to CWE-320. Impacted is confidentiality. The summary by CVE is:
An issue was discovered on Samsung 840 EVO devices. Vendor-specific commands may allow access to the disk-encryption key.
The bug was discovered 11/06/2018. The weakness was shared 11/20/2018 as confirmed advisory (CERT.org). It is possible to read the advisory at kb.cert.org. The identification of this vulnerability is CVE-2018-12038 since 06/07/2018. Attacking locally is a requirement. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 14 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 105841†). The entry VDB-127018 is related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
License
Website
- Vendor: https://www.samsung.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.1VulDB Meta Temp Score: 3.1
VulDB Base Score: 2.0
VulDB Temp Score: 2.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.2
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: Key managementCWE: CWE-320
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: No
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
06/07/2018 🔍11/06/2018 🔍
11/06/2018 🔍
11/20/2018 🔍
11/20/2018 🔍
11/21/2018 🔍
02/01/2025 🔍
Sources
Vendor: samsung.comAdvisory: kb.cert.org
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-12038 (🔍)
GCVE (CVE): GCVE-0-2018-12038
GCVE (VulDB): GCVE-100-127019
CERT: 🔍
SecurityFocus: 105841 - Self-Encrypting Drives CVE-2018-12038 Local Security Bypass Vulnerability
See also: 🔍
Entry
Created: 11/21/2018 12:12Updated: 02/01/2025 16:49
Changes: 11/21/2018 12:12 (60), 04/14/2020 09:45 (4), 02/01/2025 16:49 (16)
Complete: 🔍
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.