CVE-2018-5914
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 · uneditedImproper input validation in TZ led to array out of bound in TZ function while accessing the peripheral details using the incoming data in Snapdragon Mobile, Snapdragon Wear version MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 625, SD 650/52, SD 835, SDA660.
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 confidenceImproper input validation in the TrustZone (TZ) component of Qualcomm Snapdragon processors allows an attacker to trigger array out-of-bounds access when processing peripheral details with specially crafted incoming data, potentially leading to code execution in the secure environment or denial of service.
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 versionsall versionsall versionsall versionsall versionsall 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 modelDetermine the exact Qualcomm Snapdragon or modem model number in your device. This may be listed in device specifications, system information, or on the device board itself. Common identifiers include Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 425, or Sd 430.Affected if The model matches one of the listed affected products: Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 425, or Sd 430.
-
Verify the firmware versionLocate the firmware or baseband firmware version for the identified Qualcomm component. This is typically found in the device's about phone settings, kernel logs, or through diagnostic tools provided by the device manufacturer.Affected if The firmware version is any version of the affected model, as all versions are listed as vulnerable.
-
Confirm TrustZone is enabledVerify that the TrustZone (TZ) secure environment is active on the device. TrustZone is typically enabled by default on affected Snapdragon devices, but can be checked through security settings or by examining the secure partition information.Affected if TrustZone is enabled and operational on the device, which is the default state for vulnerable configurations.
-
Check for OEM security updatesConsult your device manufacturer's security advisory or update documentation to see if a patch addressing CVE-2018-5914 has been released for your specific device model.Affected if No vendor security patch for CVE-2018-5914 has been applied to your device firmware.
A device is affected if it contains any of the listed Qualcomm Snapdragon processors or modems (Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 425, Sd 430) and is running firmware without the vendor-supplied security patch for the TrustZone input validation vulnerability.
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 vendor-provided firmware/security patch from the device OEM that addresses the input validation vulnerability in the TrustZone component for affected Snapdragon versions.
- Consultation6.0 h
- Implementation4.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5914 — 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-2018-5914 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