CVE-2020-0329
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 the OMX encoder, there is a possible out of bounds read due to invalid input validation. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-63522940
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 confidenceThis is an out-of-bounds read vulnerability in the OMX (OpenMAX) encoder component of Android 11. The vulnerability stems from insufficient input validation, allowing a local attacker to read memory contents beyond intended boundaries without requiring any elevated privileges or user interaction, leading to potential information disclosure.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 the system property 'ro.build.version.release' or inspect 'Settings > About Phone > Android version'. The affected version is exactly 11.0 per the CVE scope.Affected if The device runs Android 11.0 (exact match required, not 10.x or 12.x)
-
Confirm OMX encoder component is presentCheck for the existence of OMX encoder libraries in the system (e.g., libOMX.*.so files in /system/lib or vendor/lib directories). List files with 'find /system -name "*OMX*"' or check /vendor/etc/seccomp policy files that reference OMX.Affected if OMX encoder libraries are present on the device
-
Identify OMX encoder usageCheck if any application or service is actively using the OMX encoder. This can be done by reviewing media codec usage via 'dumpsys media.codec' or by examining logcat output for OMX component initialization.Affected if Any app or service is using the OMX encoder for encoding operations
-
Check build fingerprint for patch levelRun 'getprop ro.build.version.security_patch' to retrieve the security patch date. Compare against the patch date for CVE-2020-0329.Affected if The security patch level predates the CVE-2020-0329 fix (device is unpatched)
A device is affected if it runs Android 11.0 exactly, has the OMX encoder component present, and has not received the corresponding security patch for CVE-2020-0329.
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 the Android security patch for CVE-2020-0329 (part of Android-11's security update cycle). For custom Android builds or products using the OMX encoder, backport the input validation fix to the encoder component.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0329 — 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-0329 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