dbcve.org
AndroidOperating system · Google

CVE-2015-6608

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
mediaserver in Android 5.x before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted media file, aka internal bugs 19779574, 23680780, 23876444, and 23658148, a different vulnerability than CVE-2015-8072 and CVE-2015-8073.

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

Memory corruption vulnerability in Android's mediaserver component allows remote attackers to execute arbitrary code via specially crafted media files. The vulnerability affects Android versions 5.x before 5.1.1 LMY48X and 6.0 before the November 2015 security patch.

MitigationApply the appropriate Android security patch (5.1.1 LMY48X or later for 5.x, November 2015 patch or later for 6.0). Avoid opening media files from untrusted sources.

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 the installed Android 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 is 5.0, 5.0.1, 5.0.2, 5.1, or 5.1.1 but earlier than the LMY48X build.
  2. Confirm the Android 5.x build number
    Go to Settings > About Phone > Build number. Verify if the build is LMY48X or later for 5.1.1. If running an earlier 5.x version, check the exact build ID via 'getprop ro.build.id' in ADB shell.
    Affected if The build ID is earlier than LMY48X on any Android 5.x release.
  3. Check Android 6.0 security patch level
    If running Android 6.0, go to Settings > About Phone > Security patch level. Alternatively, run 'getprop ro.build.version.security_patch' via ADB shell.
    Affected if The security patch level is earlier than November 2015, or the field is empty or shows an older date.
  4. Verify mediaserver component presence
    Confirm the device has media playback capability by checking if /system/bin/mediaserver exists. Run 'ls -la /system/bin/mediaserver' via ADB shell.
    Affected if The mediaserver binary exists and the Android version falls within the affected ranges above.

The device is affected if it runs Android 5.0 through 5.1.1 (with build earlier than LMY48X) or Android 6.0 with a security patch level before November 2015.

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 the appropriate Android security patch (5.1.1 LMY48X or later for 5.x, November 2015 patch or later for 6.0). Avoid opening media files from untrusted sources.

Recommended fix High confidence

Android 5.1.1 LMY48X or later for 5.x devices; Android 6.0 with November 2015 security patch (build date 2015-11-01 or later)

  1. Check the Android version on the device by navigating to Settings > About Phone > Android version
  2. For Android 5.0.x and 5.1.0 devices: Navigate to Settings > About Phone > System updates and check for available updates
  3. Upgrade to Android 5.1.1 LMY48X or later to resolve the vulnerability
  4. For Android 6.0 devices: Ensure the device receives the November 2015 security patch level (2015-11-01) or later via system update
  5. If the device manufacturer no longer provides updates, consider replacing the device with one that receives regular security patches

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $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 $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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