CVE-2017-13204
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 information disclosure vulnerability in the Android media framework (libavc). Product: Android. Versions: 7.0, 7.1.1, 7.1.2, 8.0, 8.1. Android ID: A-64380237.
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 confidenceAn information disclosure vulnerability exists in libavc (the Android media framework's H.264/AVC codec implementation). The specific nature of the exposed information and exploitation method are not detailed in available documentation, but the critical CVSS score (9.1) indicates significant potential impact.
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.0= 6.0.1= 7.0= 7.1.1= 7.1.2= 8.0= 8.1CVSS 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
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Check Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Version is 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, or 8.1
-
Check security patch levelGo to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB shellAffected if Patch level is before 2018-01-01 (for example, 2017-12-01 or earlier)
-
Verify libavc codec is in useCheck if the device uses H.264/AVC video decoding by inspecting media codecs: run 'adb shell dumpsys media.codec' or check video playback logsAffected if The device processes H.264/AVC content through libavc, which is standard on affected Android versions
The device is affected if it runs Android 6.0 through 8.1 with a security patch level earlier than 2018-01-01 and uses the libavc media codec for H.264/AVC video processing.
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 Android security patch level 2018-01-01 or later, which includes the fix for this libavc vulnerability. Users should ensure their devices receive regular Android system security updates.
Android 8.1 (or December 2017 Security Patch Level)
- 1. Determine the current Android version on the device by going to Settings > About Phone > Android version
- 2. Confirm the device is running Android 6.0, 6.0.1, 7.0, or 7.1.1 which are affected by CVE-2017-13204
- 3. Check for available system updates by going to Settings > About Phone > System Updates or Settings > System > Software Update
- 4. Apply the latest Android security update. The fix for this vulnerability was released in the December 2017 Android Security Patch Level
- 5. After updating, verify the Android version and security patch level in Settings > About Phone > Security patch level reflects December 2017 or later
- 6. If the device manufacturer has not released an update with the December 2017 patch level, consider upgrading to a device with Android 8.0 or 8.1 which includes the fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13204 — 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-13204 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