An issue was discovered on Samsung 840 EVO devices.

published 2018-11-20 7y ago modified 2026-06-17 4mo ago also EUVD-2018-4021

cvss: 4.2; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits: 0; none known

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

Patch / fix

links 1

portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180028 advisory

Is CVE-2018-12038 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	4.2	CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	1.9	AV:L/AC:M/Au:N/C:P/I:N/A:N

Classification

Weakness

CWE-522 Insufficiently Protected Credentials

References

portal.msrc.microsoft.com /en-US/security-guidance/advisory/ADV180028
patch, vendor-advisory
security.netapp.com /advisory/ntap-20181112-0001/
third-party-advisory
kb.cert.org /vuls/id/395981
third-party-advisory, us-government-resource
securityfocus.com /bid/105841
vdb-entry, third-party-advisory

Sources

CVE List CVE-2018-12038
NVD CVE-2018-12038

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.