dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2017-14913

CRITICAL · 9.8 CVSS v3.0 Published 2018-03-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In Android before 2018-01-05 on Qualcomm Snapdragon IoT, Snapdragon Mobile MDM9206, SD 625, SD 650/52, SD 835, SD 845, DDR address input validation is being improperly truncated.

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 confidence

Improper input validation in DDR memory address handling in Qualcomm Snapdragon IoT and Mobile chipsets (MDM9206, SD 625, SD 650/52, SD 835, SD 845) allows truncation of address inputs, potentially enabling memory corruption or privilege escalation. The vulnerability exists in the hardware/firmware layer before Android OS boot.

MitigationApply vendor-specific firmware/bootloader updates released after January 2018. Contact device OEMs or Qualcomm for patched baseband/firmware images; this cannot be remediated through Android application or system updates alone.

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
Mdm9206 FirmwareOperating system
Affected:all versions
Sd 625 FirmwareOperating system
Affected:all versions
Sd 650 FirmwareOperating system
Affected:all versions
Sd 652 FirmwareOperating system
Affected:all versions
Sd 835 FirmwareOperating system
Affected:all versions
Sd 845 FirmwareOperating system
Affected:all versions

CVSS 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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device chipset model
    Check the SoC/processor model via device settings (Settings > About Phone > Model/Hardware) or by running 'getprop ro.board.platform' or 'getprop ro.hardware' in ADB shell
    Affected if The chipset is one of: MDM9206, SD 625, SD 650, SD 652, SD 835, or SD 845
  2. Confirm baseband firmware version
    Check the baseband version via Settings > About Phone > Baseband version, or run 'getprop gsm.version.baseband' in ADB shell
    Affected if The device uses an affected chipset and the baseband version predates January 2018 firmware releases (patched versions vary by OEM)
  3. Check OEM firmware update status
    Check if the device has received firmware or bootloader updates from the device OEM after January 2018. Look in Settings > System > Software Update or check with the device manufacturer.
    Affected if The device OEM has not released or applied a patched baseband/firmware update for this CVE to the device

The device is affected if it uses any of the listed Qualcomm chipset models (MDM9206, SD 625, SD 650/52, SD 835, SD 845) and has not received vendor-specific firmware updates released after January 2018.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-specific firmware/bootloader updates released after January 2018. Contact device OEMs or Qualcomm for patched baseband/firmware images; this cannot be remediated through Android application or system updates alone.

Recommended fix High confidence

Android security patch level January 5, 2018 or later (includes Qualcomm firmware fix for CVE-2017-14913)

  1. Verify current Android security patch level on the device by going to Settings > About Phone > Security Patch Level
  2. Update to Android with the January 5, 2018 or later security patch level to obtain the fix
  3. If the device manufacturer has not released an update containing the January 2018 security patch, contact the device vendor for timeline or consider upgrading to a newer device model that receives current security updates
Caveat Older devices may not receive this security update; some legacy IoT devices based on MDM9206 may have limited update support

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-14913 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-14913 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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