CVE-2019-10705
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWestern Digital SanDisk X600 devices in certain configurations, a vulnerability in the access control mechanism of the drive may allow data to be decrypted without knowledge of proper authentication credentials.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe WD SanDisk X600 SSD has a vulnerability in its access control mechanism that allows data decryption without proper authentication credentials. This affects devices in certain configurations, likely involving the drive's hardware-based encryption or access control features.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< x6112100< x6112100< x6112100< x6112100< x6112100< x6112100< x6112100< x6112100CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify X600 SSD modelUse disk management tools (Windows: 'diskpart list disk', Linux: 'lsblk' or 'nvme list', or check SMART data) to identify if a WD SanDisk X600 drive is present. Model numbers include SD9TB8W and SD9TN8W variants with capacities 128G, 256G, 512G, 1T00, or 2T00.Affected if The system contains an X600 SSD with model number SD9TB8W or SD9TN8W and any of the listed capacity variants.
-
Check firmware versionRetrieve the firmware version using manufacturer tools (SanDisk Dashboard, Western Digital Dashboard, or SMART utilities like smartctl). Look for firmware version string (for example, via 'smartctl -a' on Linux or manufacturer diagnostic software on Windows).Affected if Firmware version is present and is lower than x6112100 (for example, x6011000, x6010200, etc.).
-
Verify encryption or access control statusCheck if hardware-based encryption (OPAL, eDrive) or any access control/password protection feature is enabled on the drive. On Windows, use 'manage-bde -status' or manufacturer software. On Linux, check 'cryptsetup luksDump' or drive security settings via 'smartctl --security' or NVMe commands.Affected if Hardware encryption or any access control feature is enabled on the drive (the vulnerability allows bypass of this protection).
You are affected if you have a WD SanDisk X600 SSD (SD9TB8W or SD9TN8W variant), your firmware version is below x6112100, and you have hardware-based encryption or access control features enabled on the drive.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate device firmware if available, review and harden access control configurations, or consider replacing affected drives with newer models that do not have this vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10705 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10705 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data