CVE-2014-10063
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 MDM9625 and SD 800, a fuse is not correctly blown on a secure device.
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 confidenceA hardware security vulnerability in Qualcomm Snapdragon MDM9625 and SD 800 chips where a security fuse is not correctly blown, potentially allowing bypass of secure boot or other hardware security mechanisms. This affects Android devices with these processors running security patch levels before 2018-04-05.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 processor modelCheck the device specifications or use system information to determine if the device uses a Qualcomm Snapdragon MDM9625 or SD 800 chip. On Android, this can be found in Settings > About Phone > Processor or by checking /proc/cpuinfo for chip identifiers.Affected if The device contains a Qualcomm MDM9625 or SD 800 processor
-
Check the Android security patch levelOn Android, go to Settings > About Phone > Android security patch level. Alternatively, run 'getprop ro.build.version.security_patch' via ADB shell to retrieve the current patch level.Affected if The security patch level is set to a date before April 5, 2018 (2018-04-05)
-
Confirm secure boot configurationInspect the device bootloader or secure boot settings. On affected devices, verify whether hardware security mechanisms are enabled. This may require checking the bootloader status via 'fastboot oem device-info' or similar OEM-specific commands.Affected if Secure boot is enabled but the hardware fuse flaw exists (requires both chip and patch level conditions)
A device is affected if it contains a Qualcomm MDM9625 or SD 800 chip AND is running an Android security patch level earlier than 2018-04-05.
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 April 5, 2018 or later Android security patch level, which includes the fix for this specific vulnerability in the affected Snapdragon chips.
- Consultation8.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-10063 — 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-10063 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