CVE-2018-5884
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 · uneditedImproper Access Control in Multimedia in Snapdragon Mobile and Snapdragon Wear, Non-standard applications without permission may acquire permission of Qualcomm-specific proprietary intents.
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 confidenceImproper access control vulnerability in the multimedia component of Snapdragon Mobile and Snapdragon Wear processors allows non-standard third-party applications to acquire permissions for Qualcomm-specific proprietary intents without proper authorization, potentially enabling unauthorized access to multimedia functionality.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device chipset modelCheck the processor/SOC information in device settings under 'About Phone' or by running 'getprop ro.hardware' or 'cat /proc/cpuinfo'Affected if The chipset is one of: Mdm9607, Mdm9206, Mdm9635m, Mdm9650, Sd 210, Sd 212, Sd 205, or Sd 615
-
Check the Android security patch levelGo to Settings > About Phone > Android security patch level or run 'getprop ro.build.version.security_patch'Affected if The security patch level is earlier than the month when the vendor released the fix for this CVE (consult your OEM security bulletin)
-
Verify the firmware versionCheck the baseband or modem firmware version via 'getprop gsm.version.baseband' or through the device kernel logsAffected if The firmware version matches an affected model and the device has not received a vendor-supplied security update containing the fix for CVE-2018-5884
-
Inspect for unauthorized multimedia intent permissionsReview installed applications and their requested permissions, specifically looking for apps that have obtained Qualcomm proprietary multimedia intent permissions without explicit user authorizationAffected if Any non-standard third-party application holds permissions for Qualcomm-specific proprietary multimedia intents that were not explicitly granted by the user
The device is affected if it uses any of the listed Snapdragon chipsets (Mdm9607, Mdm9206, Mdm9635m, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 615) and has not received the vendor security patch addressing this improper access control vulnerability.
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 security patches for Snapdragon processors; users should update their device firmware to the latest available security update from their OEM.
- Consultation8.0 h
- Implementation24.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 $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5884 — 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-5884 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