dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2018-11287

CRITICAL · 9.8 CVSS v3.0 Published 2018-09-20
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 Snapdragon (Automobile, Mobile, Wear) in version MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SD 845, SD 850, SDA660, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, SDM710, Snapdragon_High_Med_2016, incorrect control flow implementation in Video while checking buffer sufficiency.

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

Buffer sufficiency checking in the Video component of multiple Qualcomm Snapdragon chipsets contains an incorrect control flow implementation flaw. This logic vulnerability could allow improper buffer handling, potentially leading to memory corruption or code execution. The issue affects video processing in both mobile and automotive Snapdragon variants.

MitigationApply vendor-supplied firmware updates from Qualcomm and device OEMs. This is a hardware/firmware-level flaw requiring patches at the chipset level rather than software application updates.

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
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Sd210 FirmwareOperating system
Affected:all versions
Sd212 FirmwareOperating system
Affected:all versions
Sd205 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 in the device
    Check the device hardware specifications, system information, or use commands like 'lspci', 'lsmem', or check /proc/cpuinfo on Linux, or look at modem firmware logs (e.g., at 'AT+QGDC' or 'AT+CGMM' for Qualcomm modems)
    Affected if The chipset model matches Mdm9206, Mdm9607, Mdm9650, Msm8909w, Msm8996au, Sd210, Sd212, or Sd205
  2. Verify video processing capability is present
    Check if the device has video encoding/decoding hardware or video driver modules loaded. On Linux, examine loaded kernel modules (lsmod) for video-related drivers (video, media, venus, cvp). On Android, check /dev/video* nodes or check via 'getprop' for media-related properties
    Affected if Video hardware acceleration or video driver support is enabled on the device
  3. Check the firmware version of the affected chipset
    Query the modem or chipset firmware version. For Qualcomm modems, use AT commands such as 'AT+QGMR' or 'AT+CGMR' to retrieve firmware version information. On Android, check /vendor/firmware or use 'getprop' to find radio or modem firmware version
    Affected if The firmware version returned indicates any version of the affected chipsets (all versions are affected per the advisory)

If the device uses any of the listed Qualcomm chipset models (Mdm9206, Mdm9607, Mdm9650, Msm8909w, Msm8996au, Sd210, Sd212, Sd205) with video processing capability enabled, the environment is affected by this vulnerability.

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-supplied firmware updates from Qualcomm and device OEMs. This is a hardware/firmware-level flaw requiring patches at the chipset level rather than software application updates.

Recommended fix Moderate confidence

Android Security Patch Level October 2018 or later (device-specific; contact OEM for exact version)

  1. 1. Check the Android Security Bulletin for the month this CVE was addressed (CVE-2018-11287 was addressed in Qualcomm's October 2018 security update)
  2. 2. Contact your device manufacturer (OEM) to confirm they have released a firmware/security update that includes the fix for this CVE
  3. 3. Apply the OEM-provided system/firmware update to the affected device
  4. 4. Verify the patch level after update matches or exceeds the Android Security Patch Level that includes the fix
Caveat Firmware updates may have compatibility considerations; ensure OEM supports your device model before applying

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
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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