CVE-2015-3824
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 MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in Android before 5.1.1 LMY48I does not properly restrict size addition, which allows remote attackers to execute arbitrary code or cause a denial of service (integer overflow and memory corruption) via a crafted MPEG-4 tx3g atom, aka internal bug 20923261.
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 overflow vulnerability in libstagefright's MPEG4Extractor::parseChunk function when processing MPEG-4 tx3g atoms. The function fails to properly validate size additions during chunk parsing, allowing an attacker to trigger integer overflow leading to heap memory corruption and potential remote code execution via crafted MPEG-4 files.
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 ADB shellAffected if Version is 5.1 or below (the fix was included in 5.1.1)
-
Check 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 earlier than LMY48I (the specific patch that addressed this vulnerability)
-
Verify libstagefright component existsCheck for the presence of libstagefright.so in /system/lib/ or /vendor/lib/ via ADB shell with 'ls -la /system/lib/libstagefright.so'Affected if The library exists and the version is from Android 5.1 or earlier (vulnerable to this flaw)
-
Confirm media processing is enabledVerify that the device uses libstagefright for media playback by checking related system properties with 'getprop | grep stagefright'Affected if libstagefright is actively used for MPEG-4 file processing, which enables the attack surface for this vulnerability
A device is affected if it runs Android 5.1 or earlier, or has a security patch level earlier than LMY48I, and uses libstagefright to process MPEG-4 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 security patch level LMY48I or later which contains the fix for CVE-2015-3824 in libstagefright; alternatively, ensure Android devices are updated to version 5.1.1 or newer.
Android 5.1.1 LMY48I or later (August 2015 Android Security Patch Level)
- Upgrade the Android device to version 5.1.1 LMY48I or later to obtain the fixed libstagefright library
- Verify the Android version by navigating to Settings > About Phone > Android version
- If the device cannot be upgraded to 5.1.1, contact the device manufacturer for available security patches
- Apply any available carrier or manufacturer OTA updates that include the August 2015 Android Security Bulletin patches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3824 — 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-3824 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