CVE-2015-6600
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 · uneditedlibstagefright in Android before 5.1.1 LMY48T allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted media file, aka internal bug 22882938.
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 · high confidencelibstagefright in Android before 5.1.1 LMY48T contains a memory corruption vulnerability when processing crafted media files, allowing remote attackers to achieve arbitrary code execution or cause denial of service.
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<= 5.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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 versionNavigate to Settings > About Phone on the Android device and locate the 'Android version' or 'Build number' field. Alternatively, run 'getprop ro.build.version.release' via ADB shell.Affected if The Android version displays 5.1 or any version earlier than 5.1.1 LMY48T (such as 5.0.x, 4.4.x, 4.3.x, etc.)
-
Check for the LMY48T security patch levelNavigate to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB shell.Affected if The security patch level is empty, missing, or shows a date earlier than the August 2015 LMY48T patch release
-
Confirm libstagefright is presentVerify the libstagefright library exists on the system by running 'ls -la /system/lib/libstagefright.so' or 'ls -la /system/lib64/libstagefright.so' via ADB shell.Affected if The libstagefright library file exists on the device (this is true for virtually all Android devices running 5.1 or earlier)
A device is affected if it runs Android version 5.1 or earlier without the August 2015 LMY48T security patch, and the vulnerable libstagefright library is present on the system.
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 · scopedUpdate affected Android devices to version 5.1.1 LMY48T or later to receive the patched libstagefright library; this is a system-level patch requiring OS updates from device vendors/OEMs.
Android 5.1.1 LMY48T or later (or latest stable release for your device)
- Verify current Android version by going to Settings > About Phone > Android version
- Backup important data before upgrading
- Upgrade to Android 5.1.1 LMY48T or later (recommended: latest available stable release for your device)
- Verify the upgrade was successful by checking Settings > About Phone > Android version shows 5.1.1 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.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 $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6600 — 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-2015-6600 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