CVE-2015-6631
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 24623447.
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 information disclosure vulnerability in libstagefright (Android's media playback framework) allows remote attackers to bypass Signature or SignatureOrSystem permission protections, potentially granting elevated access to sensitive system functions or data.
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.
-
Confirm the device runs Android OSCheck the device settings under Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Device is not Android - this CVE does not apply to other operating systems
-
Determine the Android version numberNavigate to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB. Common values include 5.0, 5.1, 6.0Affected if Version is 5.0.x, 5.1.x, or 6.0 exactly - these are within the affected range
-
Check the security patch levelNavigate to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB. The fix requires patch level 5.1.1 LMY48Z or later for 5.x, or December 2015 or later for 6.0Affected if Patch level is earlier than 5.1.1 (LMY48Z) for 5.x devices, or earlier than December 2015 for 6.0 devices - these are unpatched and vulnerable
Device is affected if it runs Android 5.0 through 5.1.0 or Android 6.0 AND has a security patch level earlier than the December 2015/Android 5.1.1 LMY48Z updates.
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 appropriate Android security patch level (5.1.1 LMY48Z or later, or 6.0 with December 2015 security update or later) to affected devices. For organizations, this requires inventorying affected Android devices and coordinating with OEMs/carriers for patch deployment.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6631 — 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-6631 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