CVE-2018-3586
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 · uneditedAn integer overflow to buffer overflow vulnerability exists in the ADSPRPC heap manager in all Android releases(Android for MSM, Firefox OS for MSM, QRD Android) from CAF using the Linux kernel.
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 confidenceInteger overflow in the ADSPRPC heap manager leads to buffer overflow. The vulnerability allows heap corruption through crafted memory allocation requests that exceed intended bounds due to insufficient integer overflow checks.
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 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device runs Google AndroidRun 'getprop ro.build.id' or check /system/build.prop for ro.build.version.releaseAffected if Device is not running Android - not affected
-
Verify presence of ADSPRPC libraryCheck for /vendor/lib64/libadsprpc.so or /vendor/lib/libadsprpc.so using 'ls -la' commandAffected if The libadsprpc.so library file exists on the device - vulnerable component is present
-
Confirm device uses Qualcomm processorRun 'getprop ro.hardware' or check /proc/cpuinfo for Qualcomm SnapdragonAffected if Device uses Qualcomm Snapdragon processor - ADSPRPC is likely used
-
Check if DSP daemon is runningRun 'ps -A | grep -i adsprpc' or check for /dev/adsprpc-smd device nodeAffected if The ADSPRPC subsystem is active - attack surface is exposed
If the Android device has the Qualcomm ADSPRPC library present and the DSP subsystem is active, the environment is affected by this integer overflow vulnerability in the ADSPRPC heap manager.
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.
dbcve · scopedApply CAF/Android kernel security patches for ADSPRPC heap manager; implement proper integer overflow checks in memory allocation routines.
Any Android version with the November 2018 security patch level (2018-11-01) or later applied
- Check the Android Security Patch Level on the device by going to Settings > About Phone > Build Number or by running 'getprop ro.build.version.security_patch'
- Apply the Android Security Bulletin patch for the month when CVE-2018-3586 was addressed. According to the Android Security Bulletin, this vulnerability was addressed in the November 2018 security patch level (2018-11-01) or later
- Verify the patch has been applied by checking that the security patch level is 2018-11-01 or higher
- If the device cannot receive official patches, consider upgrading to a newer Android version that includes this fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-3586 — 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-3586 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