CVE-2015-6633
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 · uneditedThe display drivers in Android before 5.1.1 LMY48Z and 6.0 before 2015-12-01 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted media file, aka internal bug 23987307.
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 confidenceMemory corruption vulnerability in Android display drivers that can be triggered by a specially crafted media file, allowing remote attackers to execute arbitrary code or cause a denial of service.
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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 checksWork through these to decide whether this CVE applies to you.
-
Check Android OS versionOn the device, go to Settings > About Phone > Android version. Alternatively, run 'adb shell getprop ro.build.version.release' via ADB.Affected if Version is 5.0, 5.0.1, 5.0.2, 5.1, 5.1.1 before LMY48Z, or 6.0
-
Confirm build date (for 5.1.1 devices)Go to Settings > About Phone > Build number, or run 'adb shell getprop ro.build.date.utc' to get the Unix timestamp of the build.Affected if Build date is before the 2015-12-01 security patch (timestamp 1448956800) and version is 5.1.1
-
Check security patch level (for 6.0 devices)Go to Settings > About Phone > Security patch level, or run 'adb shell getprop ro.build.version.security_patch'.Affected if Patch level is earlier than December 2015 or not set
Your device is affected if it runs Android 5.0 through 5.1.1 (before LMY48Z) or Android 6.0 without the December 2015 security update.
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.
dbcve · scoped5.1.1
Apply Android security updates (5.1.1 LMY48Z or 6.0 as of 2015-12-01 or later) to affected devices; enforce patch management for Android fleets.
Android 5.1.1 (LMY48Z) or later for 5.x; Android 6.0.1 or later for 6.0
- Check the current Android version on the device in Settings > About Phone > Android version
- For Android 5.0-5.1.0 devices: Upgrade to Android 5.1.1 LMY48Z or later stable release
- For Android 6.0 devices: Upgrade to Android 6.0.1 or later which includes the December 2015 security patchset
- If the device cannot receive official OTA updates, consider flashing a factory image from the official Android developer site for the device model
- Verify the upgrade was successful by checking the Android version and security patch level in Settings > About Phone > Security patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6633 — 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-6633 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