dbcve.org
AndroidOperating system · Google

CVE-2015-3834

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 integer overflows in the BnHDCP::onTransact function in media/libmedia/IHDCP.cpp in libstagefright in Android before 5.1.1 LMY48I allow attackers to execute arbitrary code via a crafted application that uses HDCP encryption, leading to a heap-based buffer overflow, aka internal bug 20222489.

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

Integer overflows in the BnHDCP::onTransact function in libstagefright's IHDCP.cpp allow a crafted application using HDCP encryption to trigger a heap-based buffer overflow, achieving arbitrary code execution with critical severity (CVSS 10).

MitigationApply Android system update to version 5.1.1 LMY48I or later; for custom Android builds, update libstagefright with the patched IHDCP.cpp to address the integer overflows in the HDCP transaction handling.

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. Check Android version
    Go to Settings > About Phone and look at the Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Version is 5.1 or lower (the vulnerability affects Android <= 5.1)
  2. Verify libstagefright is present
    Check for the presence of libstagefright.so in /system/lib/ or /system/lib64/ via ADB: 'ls -la /system/lib/libstagefright.so'
    Affected if The library exists and is used by the Android media framework
  3. Identify HDCP module in libstagefright
    Check for IHDCP.cpp or libhdcp library in the system: 'find /system -name "*hdcp*"' via ADB
    Affected if HDCP-related components exist in the system (libhdcp.so or hdcp modules in libstagefright)
  4. Confirm vulnerable HDCP transaction handling
    Inspect the libstagefright library for the BnHDCP::onTransact function - this requires reverse engineering or checking against the unpatched IHDCP.cpp source
    Affected if The onTransact function in libstagefright contains the integer overflow without the bounds check fix

A system is affected if it runs Android version 5.1 or lower AND uses libstagefright with HDCP support, where the onTransact function in IHDCP.cpp lacks the integer overflow mitigation.

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

Apply Android system update to version 5.1.1 LMY48I or later; for custom Android builds, update libstagefright with the patched IHDCP.cpp to address the integer overflows in the HDCP transaction handling.

Recommended fix High confidence

Android 5.1.1 LMY48I or later

  1. 1. Identify the current Android version on the affected device via Settings > About Phone > Android version
  2. 2. Verify if the device is running Android 5.1 (API 22) or earlier
  3. 3. Check if the device manufacturer has released a security update containing the fix (Android 5.1.1 LMY48I or later)
  4. 4. If an OTA update is available, apply it to upgrade to Android 5.1.1 or later
  5. 5. If no OTA update is available from the manufacturer, consider upgrading to a later Android version (6.0+) if the device hardware supports it
  6. 6. Verify the Android version has been updated to 5.1.1 LMY48I or later after the upgrade
Caveat Upgrading Android versions may cause incompatibility with older applications or device-specific features; some legacy apps may no longer function properly on newer Android versions

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

Fix this in Android Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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