dbcve.org
AndroidOperating system · Google

CVE-2015-6610

HIGH · 10.0 CVSS v2.0 Published 2015-11-03
Fix available
A fix is available. Upgrade to 5.1.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 LMY48X and 6.0 before 2015-11-01 allows attackers to gain privileges or cause a denial of service (memory corruption) via a crafted application, aka internal bug 23707088.

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

libstagefright in Android versions before 5.1.1 LMY48X and 6.0 before the November 2015 security patch contains a memory corruption vulnerability (internal bug 23707088). A crafted application can exploit this to achieve privilege escalation or cause a denial of service through memory corruption in the media processing subsystem.

MitigationApply Android system updates (5.1.1 LMY48X or later for 5.x, or the November 2015 security patch or later for Android 6.0) to patch libstagefright. Users on older versions should upgrade or avoid installing untrusted applications.

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.0, < 5.1.1= 6.0

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 Android OS version
    Go to Settings > About Phone > Android version, or run 'adb shell getprop ro.build.version.release'
    Affected if Version shows 5.0, 5.1.0, or 6.0 (6.0 without security patch)
  2. Verify if version is before 5.1.1 patch
    Compare the full version string (e.g., 5.0, 5.1) against the 5.1.1 LMY48X fixed release. On the device: Settings > About Phone > Build number shows the full build identifier.
    Affected if Build is earlier than LMY48X for 5.x releases, or shows '6.0' without a later security patch level
  3. Check security patch level for Android 6.0
    If running Android 6.0, run 'adb shell getprop ro.build.version.security_patch' or check Settings > About Phone > Security patch level
    Affected if Security patch level is absent or shows a date before November 2015
  4. Confirm libstagefright component presence
    The libstagefright library is part of Android media framework and is present by default on all affected versions. No manual check needed - the version check above determines exposure.
    Affected if This step confirms the vulnerable component exists on the tested version (automatic for all 5.0-5.1.x and 6.0 builds)

A device is affected if it runs Android 5.0 through 5.1.1 prior to LMY48X build, or Android 6.0 without the November 2015 security patch installed.

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 5.1.1 or later
Fixed in 5.1.1
Interim mitigation

Apply Android system updates (5.1.1 LMY48X or later for 5.x, or the November 2015 security patch or later for Android 6.0) to patch libstagefright. Users on older versions should upgrade or avoid installing untrusted applications.

Recommended fix High confidence

Android 5.1.1 LMY48X (for 5.x branch) or Android 6.0 with November 2015 security patch (for 6.0 branch)

  1. 1. Identify the current Android version on the device (Settings > About Phone > Android version)
  2. 2. For Android 5.0 to 5.1.1 (except LMY48X): Upgrade to Android 5.1.1 LMY48X or later
  3. 3. For Android 6.0: Apply the November 2015 security update or later (system update)
  4. 4. Verify the fix by checking that the build matches LMY48X for 5.x or includes the November 2015 security patch for 6.0
  5. 5. If the device cannot receive updates from the carrier/OEM, consider replacing the device with one that receives regular security updates
Caveat Some older devices may not be eligible for OTA updates from the manufacturer/carrier; in such cases device replacement may be necessary

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6610 — 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-6610 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