dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2018-11267

HIGH · 7.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 →
80/100
Remediation priority · High
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, MDM9615, MDM9640, MDM9650, MDM9655, MSM8996AU, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 600, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SD 845, SD 850, SDA660, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, SDX20, Snapdragon_High_Med_2016, when sending an malformed XML data to deviceprogrammer/firehose it may do an out of bounds buffer write allowing a region of memory to be filled with 0x20.

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 is a memory corruption vulnerability in Qualcomm Snapdragon chipsets where malformed XML data sent to the deviceprogrammer/firehose component triggers an out-of-bounds buffer write. The vulnerability allows an attacker to overwrite a memory region with 0x20 (space characters), potentially corrupting adjacent data or control structures.

MitigationApply vendor firmware updates from Qualcomm for affected chipsets. Network-based mitigation should restrict access to the deviceprogrammer/firehose interface to prevent unauthenticated XML input.

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
Mdm9615 FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Sd210 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
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 checks

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

  1. Identify the Qualcomm chipset model
    Check the device hardware specifications, bootloader, or system information to determine the exact Snapdragon chipset variant (Mdm9206, Mdm9607, Mdm9615, Mdm9640, Mdm9650, Mdm9655, Msm8996au, or Sd210)
    Affected if The device uses any of the following chipsets: Mdm9206, Mdm9607, Mdm9615, Mdm9640, Mdm9650, Mdm9655, Msm8996au, or Sd210
  2. Verify firmware version
    Query the device firmware version through AT commands, diagnostic interfaces, or vendor-specific tools provided by the device manufacturer
    Affected if The chipset is one of the affected models and the firmware has not been patched to a version beyond the vulnerable release
  3. Check if deviceprogrammer/firehose interface is accessible
    Examine network configuration, USB debugging settings, or diagnostic port accessibility to determine if the deviceprogrammer/firehose interface is exposed to untrusted inputs
    Affected if The deviceprogrammer/firehose diagnostic interface is accessible from untrusted network segments or external connections
  4. Determine if XML input can be sent to firehose
    Review access controls, authentication requirements, and firewall rules around the diagnostic/engineering interfaces used for firmware provisioning
    Affected if Unauthenticated or untrusted XML data can be submitted to the firehose/provisioning interface

A device is affected if it uses any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9615, Mdm9640, Mdm9650, Mdm9655, Msm8996au, or Sd210) and has the deviceprogrammer/firehose interface accessible for receiving XML input.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates from Qualcomm for affected chipsets. Network-based mitigation should restrict access to the deviceprogrammer/firehose interface to prevent unauthenticated XML input.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing16.0 h
  • Review / QA8.0 h
72.0 hours of engineering $12,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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