How severe is CVE-2018-12038?

CVE-2018-12038 has a CVSS 3.x base score of 4.2, rated medium severity. It is exploitable over physical access with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2018-12038 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (46th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2018-12038?

CVE-2018-12038 affects Samsung 840 Evo Firmware. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2018-12038?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2018-12038 published?

CVE-2018-12038 was published on 2018-11-20 and last updated on 2026-06-17.

CVE-2018-12038

CVE-2018-12038 is a medium-severity vulnerability in Samsung 840 Evo Firmware with a CVSS 3.x base score of 4.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-522.

Key facts

Severity: Medium (CVSS 3.x base score 4.2)
CVSS v2: 1.9
EPSS exploit prediction: 1% (46th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-522
Affected product: Samsung 840 Evo Firmware
Published: 2018-11-20
Last modified: 2026-06-17

Description

An issue was discovered on Samsung 840 EVO devices. Vendor-specific commands may allow access to the disk-encryption key.

Frequently asked questions

What is CVE-2018-12038?: An issue was discovered on Samsung 840 EVO devices. Vendor-specific commands may allow access to the disk-encryption key.
How severe is CVE-2018-12038?: CVE-2018-12038 has a CVSS 3.x base score of 4.2, rated medium severity. It is exploitable over physical access with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2018-12038 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (46th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-12038?: CVE-2018-12038 affects Samsung 840 Evo Firmware. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-12038?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2018-12038 published?: CVE-2018-12038 was published on 2018-11-20 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:o:samsung:840_evo_firmware:-:*:*:*:*:*:*:*

More vulnerabilities in Samsung 840 Evo Firmware

CVE-2018-12037 — Medium (CVSS 4.0): An issue was discovered on Samsung 840 EVO and 850 EVO devices (only in "ATA high" mode, not vulnerable in "TCG" or…

All CVEs affecting Samsung 840 Evo Firmware →

Other CWE-522 (Insufficiently Protected Credentials) vulnerabilities

CVE-2026-7312 — Critical (CVSS 10.0): CWE‑522: Insufficiently Protected Credentials in web services in Progress Sitefinity version from 14.0.7700 to…
CVE-2026-29128 — Critical (CVSS 10.0): IDC SFX2100 Satellite Receiver firmware ships with multiple daemon configuration files for routing components (e.g.,…
CVE-2025-54863 — Critical (CVSS 10.0): Radiometrics VizAir is vulnerable to exposure of the system's REST API key through a publicly accessible configuration…
CVE-2024-12799 — Critical (CVSS 10.0): Insufficiently Protected Credentials vulnerability in OpenText Identity Manager Advanced Edition on Windows, Linux, 64…
CVE-2024-51545 — Critical (CVSS 10.0): Username Enumeration vulnerabilities allow access to application level username add, delete, modify and list…
CVE-2023-1778 — Critical (CVSS 10.0): This vulnerability exists in GajShield Data Security Firewall firmware versions prior to v4.28 (except v4.21) due to…

Browse all CWE-522 (Insufficiently Protected Credentials) vulnerabilities →