CVE-2017-13205
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 (libmpeg2). Product: Android. Versions: 7.0, 7.1.1, 7.1.2, 8.0, 8.1. Android ID: A-64550583.
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 in the Android media framework's libmpeg2 component allows unauthorized access to sensitive information. The flaw exists in how libmpeg2 handles certain media data processing, potentially exposing memory contents or other sensitive data to an attacker.
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 versionRun 'getprop ro.build.version.release' or go to Settings > About Phone > Android versionAffected if The version is 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, or 8.1
-
Verify libmpeg2 library presenceCheck for /system/lib/libmpeg2.so or /vendor/lib/libmpeg2.so using 'find /system -name libmpeg2.so' or 'ls -la /system/lib/libmpeg2.so'Affected if The libmpeg2.so library file exists on the device
-
Confirm media framework uses libmpeg2Examine /system/etc/media_codecs.xml or /etc/media_codecs.xml for entries referencing libmpeg2, or check /proc/mounts for media processing activityAffected if Media codecs or profiles reference libmpeg2 or media decoding is actively used on the device
-
Check security patch levelRun 'getprop ro.build.version.security_patch' to see the installed security patch dateAffected if The security patch level is earlier than the fix date for A-64550583 (Android security patch for the affected version)
The device is affected if it runs Android 6.0 through 8.1 and contains the vulnerable libmpeg2 library used for media 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 the Android security patch for the affected versions (7.0, 7.1.1, 7.1.2, 8.0, 8.1) which includes the fix for A-64550583, or update the libmpeg2 library to the patched version.
Android 8.0 or later, or ensure security patch level is January 2018 or later
- 1. Check the current Android security patch level on the device: Settings > About Phone > Security Patch Level
- 2. If the security patch level is earlier than January 2018, apply the latest available system update from your device manufacturer
- 3. If no update is available from the manufacturer, consider upgrading to a newer Android version (8.0 or later) that includes the fix
- 4. After updating, verify the security patch level reflects January 2018 or later in Settings > About Phone > Security Patch Level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13205 — 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-13205 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