CVE-2020-0332
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 · uneditedIn libstagefright, there is a possible dead loop due to an uncaught exception. This could lead to remote denial of service with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-124783982
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 confidenceIn libstagefright (Android's media framework), an uncaught exception causes a dead/infinite loop, leading to a denial of service condition. Exploitation requires user interaction (likely opening a crafted media file) but no additional execution privileges.
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= 11.0CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
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.
-
Verify Android version is 11.0Check device Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Android version equals 11.0 exactly (versions before or after 11.0 are not affected per the listed scope)
-
Confirm libstagefright is present on the deviceCheck for the presence of libstagefright.so in /system/lib/ or /vendor/lib/ directories via ADB shell with 'ls -la /system/lib/libstagefright*'Affected if libstagefright library exists on the device (this component is present in all Android 11.0 builds)
-
Determine if media file processing is enabledCheck if apps can process media files by verifying no MDM policy blocks media file handling, or test by attempting to open an untrusted media file in a media-handling appAffected if Media processing is permitted and no policy blocks handling of untrusted media files (the exploit requires user to open a crafted media file)
-
Identify if device receives regular security updatesCheck last security patch level via Settings > Security > Security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if Security patch level is earlier than the fix for CVE-2020-0332 (patches released in Android 11's October 2020 security update)
A device is affected if it runs Android version 11.0 exactly and has not received the corresponding security patch that fixes CVE-2020-0332.
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.
From vendor dataApply Android's monthly security updates for Android 11; organizations can implement MDM policies to restrict processing of untrusted media files until patches are deployed.
- Consultation4.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 $2,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0332 — 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-2020-0332 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