CVE-2015-6611
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 · uneditedmediaserver in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to obtain sensitive information, and consequently bypass an unspecified protection mechanism, via unknown vectors, aka internal bugs 23905951, 23912202, 23953967, 23696300, 23600291, 23756261, 23541506, 23284974, 23542351, and 23542352, a different vulnerability than CVE-2015-8074.
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 confidencemediaserver in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 contains an information disclosure vulnerability allowing remote attackers to obtain sensitive information via unknown vectors, bypassing unspecified protection mechanisms. The vulnerability involves multiple internal bugs in the mediaserver component.
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.
-
Check the Android OS versionGo to Settings > About Phone (or About Device) > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Version is 5.0, 5.1.0, or 6.0 (the exact version string can be verified with 'getprop ro.build.version.sdk' returning 21, 22, or 23)
-
Check the Android security patch levelGo to Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' via ADB shellAffected if Patch level is empty, earlier than 2015-11-01, or not present on the device
-
Verify mediaserver service is presentRun 'ps | grep mediaserver' or 'getprop | grep mediaserver' via ADB shell to confirm the mediaserver process or service existsAffected if mediaserver is running (which is the default state on vulnerable Android versions)
-
Confirm no workaround or configuration change is in placeCheck /system/etc/permissions or /data for any custom XML that might restrict mediaserver permissions. Run 'dumpsys media.player' via ADB to inspect mediaserver configurationAffected if No custom restrictions are found (the default vulnerable state)
The device is affected if it runs Android 5.0 through 5.1.0 (SDK 21-22) or Android 6.0 (SDK 23) with a security patch level earlier than November 2015, with the default mediaserver configuration intact.
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 Android system updates (5.1.1 LMY48X or later for Lollipop, or November 2015 patch level or later for Marshmallow) to address the mediaserver information disclosure vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6611 — 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-6611 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