dbcve.org
AndroidOperating system · Google

CVE-2015-6604

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 23129786.

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 media framework) allows remote attackers to execute arbitrary code or cause denial of service via a crafted media file. The vulnerability affects Android versions prior to 5.1.1 LMY48T and is caused by improper handling of media file parsing.

MitigationUpdate affected Android devices to version 5.1.1 LMY48T or later. If patching is not feasible, restrict media file handling from untrusted sources and disable automatic media playback.

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 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 lower (e.g., 5.0.x, 4.4.x, 4.3.x, etc.)
  2. Check security patch level
    Go to Settings > About Phone > Build number (or go to Settings > Security > Security patch level). Alternatively, run 'getprop ro.build.version.security_patch' via ADB shell.
    Affected if The patch level is earlier than 2015-07-01 or is not listed as LMY48T (or later)
  3. Verify libstagefright is present
    Check if the device uses libstagefright for media processing. On Android 5.0-5.1, libstagefright is the default media framework. Run 'pm list packages -f | grep stagefright' via ADB shell to verify the library exists.
    Affected if libstagefright is present and the Android version is 5.1 or below
  4. Confirm automatic media playback is enabled
    Check Settings > Auto-play videos or Settings > Developer options > Media > Automatic media playback. Some devices have this in Settings > Storage > Auto-play videos.
    Affected if Automatic media playback from any source is enabled and the device runs Android 5.1 or lower

If the Android version is 5.1 or below and the security patch level is earlier than LMY48T, the device is likely affected by this vulnerability.

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. If patching is not feasible, restrict media file handling from untrusted sources and disable automatic media playback.

Recommended fix High confidence

Android 5.1.1 LMY48T or later (preferably latest available version)

  1. Check the current Android version on the device by navigating to Settings > About Phone > Android version
  2. Verify the device model is eligible for the Android 5.1.1 update by checking the manufacturer's support website
  3. Back up all important data on the device before performing the update
  4. Apply the Android 5.1.1 LMY48T or later security update through Settings > About Phone > System Updates or via OTA (Over-The-Air) update
  5. Alternatively, flash the device with a factory image containing Android 5.1.1 LMY48T or later using the manufacturer's flashing tools
  6. After the update completes, verify the device is running Android 5.1.1 LMY48T or higher by checking Settings > About Phone > Android version
Caveat Major OS upgrades may affect app compatibility, remove deprecated APIs, or reset some settings; review app compatibility before upgrading

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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