dbcve.org
AndroidOperating system · Google

CVE-2015-3832

HIGH · 10.0 CVSS v2.0 Published 2015-10-01
Fix available
A fix is available. Upgrade to after 5.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
Multiple buffer overflows in MPEG4Extractor.cpp in libstagefright in Android before 5.1.1 LMY48I allow remote attackers to execute arbitrary code via invalid size values of NAL units in MP4 data, aka internal bug 19641538.

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

Buffer overflow vulnerability in libstagefright's MPEG4Extractor component where improper validation of size values in NAL (Network Abstraction Layer) units within MP4 video files allows remote attackers to overflow buffers and execute arbitrary code via specially crafted MP4 files.

MitigationUpdate Android devices to version 5.1.1 LMY48I or later which contains the patched libstagefright; avoid opening untrusted MP4 files from unknown sources until the update is applied.

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.1

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. Verify Android version
    Check the device Android version in Settings > About Phone > Android version. Alternatively, run 'getprop ro.build.version.release' via ADB or 'adb shell getprop ro.build.version.release'
    Affected if The version listed is 5.1 or earlier (5.0, 4.x, etc.)
  2. Confirm libstagefright library presence
    Check if the libstagefright library exists on the device. On most Android devices, it is located at /system/lib/libstagefright.so. Use 'ls -la /system/lib/libstagefright.so' via ADB shell or file manager with root access
    Affected if The library file exists on the device, indicating the vulnerable component is present
  3. Verify MPEG4 media handling capability
    Confirm the device can play MP4 files, which requires the MPEG4Extractor component. Attempt to play an MP4 file or check media profiles in /system/etc/media_profiles.xml for MPEG4 support
    Affected if MPEG4 playback is supported, meaning the MPEG4Extractor component is active and vulnerable to malicious MP4 files
  4. Check for untrusted MP4 file processing exposure
    Determine if the device routinely processes MP4 files from untrusted sources such as web browsers, messaging apps, or email attachments. Review installed applications that handle media files
    Affected if Applications that automatically process incoming MP4 files (browsers, chat apps, email clients) are in regular use, creating an attack vector for the vulnerability

A device is affected if it runs Android version 5.1 or earlier, contains the libstagefright library with MPEG4Extractor support, and has applications that process MP4 files from potentially untrusted sources.

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 a release after 5.1
Interim mitigation

Update Android devices to version 5.1.1 LMY48I or later which contains the patched libstagefright; avoid opening untrusted MP4 files from unknown sources until the update is applied.

Recommended fix High confidence

Android 5.1.1 LMY48I or later

  1. Identify the current Android version on the affected device
  2. Navigate to Settings > About Phone (or About Device) > Software Updates
  3. Check for available system updates from the device manufacturer
  4. If an update to Android 5.1.1 LMY48I or later is available, download and install it
  5. After updating, verify the device is running Android 5.1.1 LMY48I or higher to confirm the vulnerability is patched

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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