CVE-2015-3874
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 Sonivox components in Android before 5.1.1 LMY48T allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted media file, aka internal bugs 23335715, 23307276, and 23286323.
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 confidenceA memory corruption vulnerability in the Sonivox media player component of Android versions prior to 5.1.1 LMY48T allows remote code execution or denial of service via a specially crafted media file. The vulnerability stems from multiple flaws (bugs 23335715, 23307276, 23286323) in how Sonivox parses media 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 your Android OS versionGo to Settings > About Phone (or About Device) > Android version. Alternatively, run `getprop ro.build.version.release` via ADB shell.Affected if The Android version displayed is 5.1 (Build LMY47V, LMY48M, etc.) or lower. Versions 5.1.1 LMY48T and later are patched.
-
Verify Sonivox media component presenceCheck if the Sonivox (libsonivox.so) library exists on the device. Run `find /system/lib -name libsonivox*` or `find /vendor/lib -name libsonivox*` via ADB shell.Affected if The library files libsonivox.so or libsonivox-arm.so are present on the device.
-
Identify apps using Sonivox for media parsingReview installed apps that handle media playback, especially from external or untrusted sources (e.g., browsers, messaging apps, file managers). Check app permissions for storage or internet access.Affected if Apps that process media files from web downloads, attachments, or external storage are installed and regularly used.
If your Android version is 5.1 or lower and you have the Sonivox library present, you are potentially affected when processing media files from any source.
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 Android devices to version 5.1.1 LMY48T or later to patch the Sonivox component vulnerabilities; for unpatchable devices, consider disabling media file handling for untrusted sources.
Android 5.1.1 LMY48T or later
- Upgrade the Android device to version 5.1.1 (LMY48T) or later to remediate this vulnerability
- Verify the Android version by navigating to Settings > About Phone > Android version
- After upgrading, ensure Sonivox media components are updated to the latest version available in the system update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3874 — 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-3874 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