dbcve.org
AndroidOperating system · Google

CVE-2015-6599

HIGH · 10.0 CVSS v2.0 Published 2015-10-06
Fix available
A fix is available. Upgrade to after 5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
libstagefright 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 23416608.

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 confidence

A memory corruption vulnerability in libstagefright, Android's multimedia framework, affecting versions before 5.1.1 LMY48T. Attackers can exploit this by tricking users into processing a crafted media file, enabling remote code execution or causing a denial of service.

MitigationUpdate affected Android devices to version 5.1.1 LMY48T or later, or apply the vendor-supplied security patch for libstagefright.

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
AndroidOperating system
Affected:<= 5.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check the Android OS version
    Go to Settings > About Phone (or About Device) > Android version. Alternatively, run `getprop ro.build.version.release` via ADB shell.
    Affected if The version displayed is 5.1 or earlier, specifically below 5.1.1 LMY48T (such as 5.0.x, 4.4.x, or earlier)
  2. Confirm the Android build number
    In Settings > About Phone, note the Build number. Alternatively, run `getprop ro.build.id` via ADB shell.
    Affected if The build ID is earlier than LMY48T (for example, LMY47V, LMY45X, or any build from 5.0.x or 4.x branches)
  3. Identify the libstagefright component version
    Check the system library file at /system/lib/libstagefright.so. Run `ls -la /system/lib/libstagefright.so` via ADB shell, or use a file explorer app to locate the library.
    Affected if The library exists on the device (which is standard on Android 5.1 and below) and the library file date or version correlates to a pre-5.1.1 release
  4. Determine if the device receives security updates
    Check Settings > About Phone > Security patch level (if available on the device). Alternatively, run `getprop ro.build.version.security_patch` via ADB shell.
    Affected if The Security patch level is empty, missing, or dated before the August 2015 security update that addressed this CVE

The device is affected if it runs Android version 5.1 or earlier and has not received the August 2015 libstagefright security patch (builds before LMY48T).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 5.1
Interim mitigation

Update affected Android devices to version 5.1.1 LMY48T or later, or apply the vendor-supplied security patch for libstagefright.

Recommended fix High confidence

Android 5.1.1 LMY48T or later (Android 6.0+ recommended for ongoing security support)

  1. Verify current Android version by navigating to Settings > About Phone > Android version
  2. If running Android 5.1 or earlier, check for system updates by going to Settings > About Phone > Check for updates
  3. Apply any available system updates to reach Android 5.1.1 LMY48T or higher
  4. If the device manufacturer has stopped providing updates, consider migrating to a newer device that receives active security patches
  5. For enterprise environments, implement MDM (Mobile Device Management) solutions to enforce minimum OS version requirements
  6. Disable auto-fetching of multimedia messages (MMS) from unknown senders as a temporary mitigation until the upgrade can be applied
Caveat Major Android upgrades may reset some device settings, remove incompatible apps, or require reconfiguration; backup data before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6599 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-6599 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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