CVE-2015-1539
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 · uneditedMultiple integer underflows in the ESDS::parseESDescriptor function in ESDS.cpp in libstagefright in Android before 5.1.1 LMY48I allow remote attackers to execute arbitrary code via crafted ESDS atoms, aka internal bug 20139950, a related issue to CVE-2015-4493.
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 confidenceInteger underflow vulnerabilities in the ESDS::parseESDescriptor function within libstagefright's ESDS.cpp allow remote attackers to execute arbitrary code via specially crafted ESDS atoms in media files. This affects Android devices before version 5.1.1 (LMY48I).
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.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Version is 5.1 or earlier (5.1.1 LMY48I and later are patched)
-
Verify libstagefright is presentCheck for /system/lib/libstagefright.so on the device, or look for stagefright-related libraries in the system partitionAffected if The library exists (it is present in all Android versions up to 5.1) and the OS version is vulnerable
-
Identify media processing appsReview installed apps that handle audio/video files - typical candidates include browsers, messaging apps, media players, and file managersAffected if Any app that parses MPEG-4 or 3GP media files is a potential attack vector for this vulnerability
Your device is affected if it runs Android 5.1 or earlier and contains the libstagefright library, since the vulnerability lies in how this library parses ESDS atoms within media files.
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 · scopedApply Android system update LMY48I or later to patched devices; avoid processing untrusted media files until update is applied.
Android 5.1.1 LMY48I or later
- Update your Android device to version 5.1.1 (LMY48I) or later to patch the integer underflow vulnerability in libstagefright
- Verify the Android version by navigating to Settings > About Phone > Android version
- If your device cannot be updated to 5.1.1 or later, contact your device manufacturer for available security patches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1539 — 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-1539 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