CVE-2017-0876
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 · uneditedA remote code execution vulnerability in the Android media framework (libavc). Product: Android. Versions: 6.0. Android ID A-64964675.
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 confidenceA remote code execution vulnerability exists in Android's media framework component libavc (H.264/AVC codec) affecting Android 6.0. The vulnerability allows remote attackers to execute arbitrary code via specially crafted media files processed by the libavc decoder, likely through a buffer overflow or similar memory corruption issue in the codec parsing logic.
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= 6.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 Android version is 6.0Run 'getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if The version returned is exactly 6.0 (API level 23)
-
Check if libavc is present on the deviceLook for libavc.so in /system/lib/ or /vendor/lib/ directories using 'find /system/lib -name libavc*'Affected if libavc.so exists on the device
-
Identify applications or processes that use libavcSearch for apps that process media (video players, camera apps, video editors) or check which apps link to libavc via 'adb shell dumpsys meminfo' for media-related processesAffected if Any app that processes H.264 media is installed and used
-
Check the Android security patch levelRun 'getprop ro.build.version.security_patch' or check Settings > About Phone > Security patch levelAffected if The patch level is earlier than the month containing the fix for A-64964675 (the CVE fix date)
-
Test media processing with untrusted filesAttempt to decode a specially crafted H.264 file using a media player or the stagefright tool on the deviceAffected if The device can process untrusted media files without crashing or the process completes without error (noting that successful exploitation would cause a crash or unexpected behavior)
A device is affected if it runs Android 6.0, contains the vulnerable libavc library, processes untrusted H.264 media files, and has a security patch level predating the CVE fix.
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 the Android security patch level for the month containing the fix for A-64964675, which addresses the libavc vulnerability in the media framework. For affected embedded devices, update the underlying Android system image and verify media processing functionality post-patch.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0876 — 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-2017-0876 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