CVE-2015-6632
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 LMY48Z and 6.0 before 2015-12-01 allows remote attackers to obtain sensitive information, and consequently bypass an unspecified protection mechanism, via unknown vectors, as demonstrated by obtaining Signature or SignatureOrSystem access, aka internal bug 24346430.
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 vulnerability in libstagefright allows remote attackers to obtain sensitive information that can be used to bypass unspecified protection mechanisms, enabling the attacker to achieve Signature or SignatureOrSystem access privileges on affected Android devices.
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.0, < 5.1.1= 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 (or About Device) > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Version is 5.0, 5.0.1, 5.0.2, 5.1, or 6.0 (note: 5.1.1 is NOT affected)
-
Check security patch levelGo to Settings > About Phone > Build number, or run 'getprop ro.build.version.security_patch' via ADB shellAffected if Patch level is earlier than December 2015, or the property is empty/missing (indicating unpatched)
-
Verify libstagefright component presenceCheck for libstagefright library at /system/lib/libstagefright.so, or run 'pm list packages | grep stagefright' via ADB shellAffected if The library exists (this component is present by default on Android 5.0+ and required for the vulnerability to apply)
-
Confirm affected Android release branchRun 'getprop ro.build.version.sdk' via ADB shell to get the API levelAffected if SDK version is 21 (Android 5.0), 22 (Android 5.1), or 23 (Android 6.0) - note that SDK 22 with 5.1.1 build is NOT affected
A device is affected if it runs Android 5.0-5.1 (before 5.1.1) or Android 6.0, AND has a security patch level earlier than December 2015 (or no patch level set).
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 data5.1.1
Apply the Android security patch level from December 2015 or later (Android 5.1.1 LMY48Z or Android 6.0 with the December 2015 bulletin). Update all affected devices through the device manufacturer's firmware release process.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6632 — 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-6632 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