CVE-2014-10047
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 · uneditedIn Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile SD 400 and SD 800, when writing the Full Disk Encryption key to crypto engine, information leak could occur.
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 · high confidenceOn Qualcomm Snapdragon SD 400 and SD 800 processors, an information leak vulnerability exists in the Full Disk Encryption (FDE) key handling path. When the FDE key is written to the crypto engine, improper handling allows key material to potentially be exposed or leaked before it is properly protected in secure hardware. This affects Android systems before the 2018-04-05 security patch level.
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 dataall versionsall versionsCVSS 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.0/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 the Qualcomm processor modelCheck the device specifications or use a system info app to determine if the device uses a Snapdragon SD 400 or SD 800 processor. On Android, this can often be found under Settings > About Phone > Hardware info, or by checking /proc/cpuinfo for chip identification.Affected if The device is confirmed to use a Qualcomm Snapdragon SD 400 or SD 800 processor.
-
Check if Full Disk Encryption is enabledOn Android, verify FDE status by checking the device encryption settings under Settings > Security > Encryption, or by running 'getprop ro.crypto.state' and 'getprop vold.decrypt' in ADB shell. FDE shows as 'encrypted' when enabled.Affected if Full Disk Encryption is enabled and the device uses the affected Qualcomm processors.
-
Verify the Android security patch level dateCheck the Android security patch level by going to Settings > About Phone > Security patch level, or by running 'getprop ro.build.version.security_patch' in ADB shell. This displays the date in YYYY-MM-DD format.Affected if The security patch level is earlier than 2018-04-05, meaning the device has not received the fix for this vulnerability.
A device is affected if it uses a Qualcomm Snapdragon SD 400 or SD 800 processor, has Full Disk Encryption enabled, and has a security patch level earlier than April 5, 2018.
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 dataApply the Android security patch level from April 5, 2018 or later, which contains the fix for this FDE key information leak in the Qualcomm crypto subsystem. Organizations should inventory affected devices and ensure they receive OEM firmware updates.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-10047 — 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-2014-10047 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