dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2018-5867

HIGH · 7.8 CVSS v3.0 Published 2019-01-18
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
Lack of checking input size can lead to buffer overflow In WideVine in snapdragon automobile, snapdragon mobile and snapdragon wear in versions MDM9206, MDM9607, MDM9635M, MDM9650, MDM9655, MSM8996AU, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 650/52, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SDA660, SDM439, SDM630, SDM660, SDX24, Snapdragon_High_Med_2016, SXR1130

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 overflow vulnerability in WideVine DRM due to missing input size validation. The flaw allows potential code execution or denial of service by overflowing a buffer with oversized input data. Affects multiple Qualcomm Snapdragon chipset generations across automotive, mobile, and wearable platforms.

MitigationApply vendor-supplied firmware/security updates from Qualcomm and device OEMs. WideVine may receive updates through Google Play Services or OEM firmware channels. Until patches are available, minimize exposure by avoiding untrusted media content and maintaining current device software.

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
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 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 in the device
    On Android, check the device info under Settings > About Phone > Chipset or use the command: 'getprop ro.hardware' or 'cat /proc/cpuinfo' to retrieve the chipset identifier
    Affected if The chipset matches any of these: Mdm9206, Mdm9607, Mdm9635m, Mdm9650, Mdm9655, Msm8996au, Sd 210, or Sd 212
  2. Check the firmware version of the identified Qualcomm chipset
    Access the baseband or modem firmware version through Android settings (Settings > About Phone > Baseband version) or use: 'getprop gsm.version.baseband'
    Affected if The firmware version is any version (all versions of these chipsets are affected)
  3. Confirm WideVine DRM is present on the device
    Check for WideVine DRM licensing support by going to Google Settings > Play Protect > Certification status, or inspect DRM info via an app like 'DRM Info' from the Play Store
    Affected if WideVine DRM is present and active on the device
  4. Verify the device is running WideVine-protected media content handling
    Observe if the device processes DRM-protected streaming content from services like Netflix, Amazon Prime Video, or Google Play Movies - WideVine is invoked when such content is played
    Affected if The device processes WideVine-protected media content from streaming services
  5. Check the Android security patch level as firmware update indicator
    Go to Settings > About Phone > Android security patch level, or use: 'getprop ro.build.version.security_patch'
    Affected if The security patch level is older than the vendor-supplied fix date for this CVE (indicating unpatched firmware)

A user is affected if their device contains any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9635m, Mdm9650, Mdm9655, Msm8996au, Sd 210, Sd 212) and runs WideVine DRM to process protected media content, with firmware versions that have not been updated with the vendor fix.

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-supplied firmware/security updates from Qualcomm and device OEMs. WideVine may receive updates through Google Play Services or OEM firmware channels. Until patches are available, minimize exposure by avoiding untrusted media content and maintaining current device software.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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