CVE-2018-5868
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 · uneditedLack of checking input size can lead to buffer overflow In WideVine in snapdragon automobile and snapdragon mobile in versions MSM8996AU, SD 425, SD 430, SD 450, SD 625, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SDA660, SDX24, 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 confidenceBuffer overflow vulnerability in WideVine DRM due to missing input size validation. The flaw exists in Snapdragon mobile and automotive chipsets (MSM8996AU, SD 425, SD 430, SD 450, SD 625, SD 712/SD 710/SD 670, SD 820, SD 820A, SD 835, SD 845/SD 850, SDA660, SDX24, SXR1130), potentially allowing arbitrary code execution or service denial via crafted media content.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device chipset or SoC modelOn Android, check Settings > About Phone > Model/Model Number, then look up the chipset via the device specifications. On automotive head units, check the system info or firmware details.Affected if The chipset matches one of: MSM8996AU, SD 425, SD 430, SD 450, SD 625, SD 712, SD 710, SD 670, SD 820, SD 820A, SD 835, SD 845, SD 850, SDA660, SDX24, or SXR1130
-
Confirm WideVine DRM is in useCheck if the device or application uses WideVine DRM for media playback. This is typically visible in DRM info settings (Settings > Security > DRM info on Android) or in streaming app license details.Affected if WideVine DRM is enabled or used for content protection on the device
-
Verify the firmware versionCheck the firmware/baseband version in the device settings (Settings > About Phone > Baseband version or Software version). Compare against the affected product list.Affected if The firmware version corresponds to any of the listed affected chipsets (all versions are affected per the advisory)
The device is likely affected if it uses any of the listed Qualcomm Snapdragon chipsets and WideVine DRM is enabled for media playback.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied firmware/ROM updates from Qualcomm and device OEMs. Until patches are available, limit exposure by restricting media playback on affected devices and monitoring for exploitation attempts.
- Consultation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5868 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-5868 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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