dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10424

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-18
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-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, MDM9650, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 820, SD 820A, SD 835, SD 845, and SD 850, upgrading LibPNG from 1.6.12 to 1.6.21 fixes multiple issues with different CWEs.

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

This vulnerability stems from multiple security issues in LibPNG version 1.6.12 that were addressed by upgrading to version 1.6.21. The affected versions of LibPNG were distributed within Android security patch levels before April 5, 2018 on various Qualcomm Snapdragon Mobile, Automobile, and Wear chipsets, including MDM9206, MDM9650, SD 210/212/205, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 820, SD 820A, SD 835, SD 845, and SD 850.

MitigationApply the Android security patch level from April 2018 or later, or manually upgrade the LibPNG library to version 1.6.21 or higher on affected devices to resolve the multiple memory corruption vulnerabilities.

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
Mdm9650 FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 410 FirmwareOperating system
Affected:all versions
Sd 412 FirmwareOperating system
Affected:all versions
Sd 425 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 Qualcomm chipset model
    Check the device specifications or use a system info app to determine if the chipset is one of: MDM9206, MDM9650, SD 210, SD 212, SD 205, SD 410, SD 412, SD 425, SD 430, SD 450, SD 615, SD 616, SD 415, SD 617, SD 625, SD 650, SD 652, SD 800, SD 808, SD 820, SD 820A, SD 835, SD 845, or SD 850
    Affected if The device uses any of the listed Qualcomm Snapdragon chipsets and the LibPNG version is below 1.6.21
  2. Check the LibPNG library version
    Locate the libpng library file on the Android device (typically in /system/lib/ or /vendor/lib/) and run: strings libpng*.so | grep "libpng version" or use a file analysis tool to read the version metadata
    Affected if The installed LibPNG version is 1.6.12 or earlier, or any version below 1.6.21
  3. Verify the Android security patch level
    Go to Settings > About Phone > Build Number, or use 'getprop ro.build.version.security_patch' via ADB shell to retrieve the security patch date
    Affected if The security patch level is dated before April 5, 2018

A device is affected if it uses any of the listed Qualcomm chipsets with LibPNG versions below 1.6.21 and has an Android security patch level dated before April 5, 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 the Android security patch level from April 2018 or later, or manually upgrade the LibPNG library to version 1.6.21 or higher on affected devices to resolve the multiple memory corruption vulnerabilities.

Recommended fix High confidence

LibPNG 1.6.21 (or later) via OEM firmware update with Android security patch level 2018-04-05 or later

  1. Contact your device OEM (Original Equipment Manufacturer) to obtain the specific firmware update that addresses CVE-2016-10424
  2. The OEM firmware update should include the LibPNG library upgraded to version 1.6.21 or later
  3. Apply the OEM-provided security patch/update to your device
  4. Verify the security patch level after updating - the fix is included in Android security patch levels dated 2018-04-05 or later
Caveat Firmware updates require device downtime and should be tested in a staging environment before production deployment; some legacy devices may no longer receive OEM updates

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10424 — 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-2016-10424 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