CVE-2017-13300
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 denial of service vulnerability in the Android media framework (libhevc). Product: Android. Versions: 6.0, 6.0.1. Android ID: A-71567394.
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 denial of service vulnerability in Android's libhevc media codec library (HEVC/H.265). The vulnerability allows remote attackers to cause device reboot or service disruption via specially crafted media files processed by the libhevc component.
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.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 versionGo to Settings > About Phone and verify the Android version is exactly 6.0 or 6.0.1. This vulnerability only affects these specific versions.Affected if Android version is 6.0 or 6.0.1 (proceed to next checks). If version is 7.0 or higher, the device is not affected by this specific CVE.
-
Check Security Patch LevelGo to Settings > About Phone > Security patch level. Verify the date of the installed security update.Affected if Security patch level is before October 2017. If the date shows October 2017 or later, the fix is present and the device is not vulnerable.
-
Check for libhevc library presenceExamine the system library directory for the presence of libhevc (typically located at /system/lib/libhevc.so or /vendor/lib/libhevc.so). On unrooted devices, this check may require manufacturer support or diagnostic tools.Affected if The libhevc library file exists on the device and the above version/patch checks indicate vulnerability. The presence of this library is required for the exploit to function.
-
Check HEVC/H.265 codec usageMonitor or review device logs when processing HEVC/H.265 media files. Check if any applications utilize HEVC decoding capabilities.Affected if The device actively processes HEVC/H.265 content using libhevc. The vulnerability is triggered specifically when specially crafted HEVC media files are processed by this component.
A device is affected only if it runs Android 6.0 or 6.0.1, has a Security Patch Level before October 2017, contains the libhevc library, and processes HEVC/H.265 media content.
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 Android security patch level October 2017 or later, which contains the fix for this libhevc vulnerability. For end-of-life devices running Android 6.0/6.0.1, consider device replacement or network-level filtering of untrusted HEVC content.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13300 — 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-13300 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