CVE-2015-3875
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 · uneditedlibutils in Android before 5.1.1 LMY48T allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted audio file, aka internal bug 22952485.
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 · moderate confidenceMemory corruption vulnerability in Android's libutils library allows remote attackers to execute arbitrary code or cause denial of service via a crafted audio file. The vulnerability affects Android versions prior to 5.1.1 LMY48T.
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 versionNavigate to Settings > About Phone > Android version, or execute 'getprop ro.build.version.release' via ADB shellAffected if The displayed version is 5.1 or lower (5.1.0, 5.0.x, 4.4.x, etc.) indicating the device did not receive the 5.1.1 LMY48T security patch
-
Verify build fingerprint or IDRun 'getprop ro.build.fingerprint' or 'getprop ro.build.id' via ADB shell to confirm the exact buildAffected if The build ID is earlier than LMY48T (for example, LMY47V, LMY45D, etc.) on Android 5.1 or below
-
Confirm libutils library is presentThe libutils.so library resides at /system/lib/libutils.so on 32-bit or /system/lib64/libutils.so on 64-bit devices. Verify existence via ADB: 'ls -l /system/lib/libutils.so'Affected if The library exists and the Android version is 5.1 or below, meaning the vulnerable code path is present on the device
A device running Android version 5.1 or lower with the libutils library present is affected; the device must be updated to 5.1.1 LMY48T or later to resolve the vulnerability.
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 · scopedUpdate affected Android devices to version 5.1.1 LMY48T or later to patch the vulnerability in libutils. Users should avoid opening audio files from untrusted sources until the update is applied.
Android 5.1.1 LMY48T or later (preferably Android 6.0+ for extended security support)
- Verify the current Android version by navigating to Settings > About Phone > Android version
- Check if the device manufacturer has released Android 5.1.1 LMY48T or a later security patch for your specific device model
- If an update is available, navigate to Settings > About Phone > System Updates > Check for Updates
- Download and install the available update
- After updating, verify the Android version shows 5.1.1 or higher and confirm the security patch level in Settings > About Phone > Security patch level
- If no official update is available from the device manufacturer, consider migrating to a device that receives regular security updates or explore custom ROMs that include the security patch (note: this may void warranty)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3875 — 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-3875 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