CVE-2022-20202
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 ih264_resi_trans_quant_4x4_sse42 of ih264_resi_trans_quant_sse42.c, there is a possible out of bounds read due to a heap buffer overflow. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-12LAndroid ID: A-204704614
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 heap buffer overflow in the ih264_resi_trans_quant_4x4_sse42 function of the H.264 video decoder allows an out-of-bounds read, potentially exposing sensitive heap memory contents to an attacker via a specially crafted media file.
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= 12.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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Check Android versionGo to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADB shellAffected if Version is exactly 12.1 (Android 12L)
-
Identify H.264 decoder libraryLook for libavc or similar H.264 decoder libraries in /system/lib or /vendor/lib directories; check library names containing 'avc' or 'h264'Affected if The vulnerable ih264_resi_trans_quant_4x4_sse42 function exists in the installed decoder library
-
Confirm media playback capabilityCheck if any video playback applications or services are installed that can process H.264 media filesAffected if H.264 decoding functionality is present and accessible on the device
-
Verify patch statusCheck system security patch level in Settings > About Phone > Security patch level or run 'getprop ro.build.version.security_patch'Affected if Security patch level is earlier than the fix release for CVE-2022-20202
A device is affected if it runs Android 12.1, contains the vulnerable H.264 decoder with the ih264_resi_trans_quant_4x4_sse42 function, and has not received the corresponding security patch.
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 · scopedApply security patches from Google/Android for Android-12L; users should avoid opening untrusted media files until the device receives the update.
Android-13 or later with corresponding security patch level
- Upgrade the Android device to a later security patch level that includes the fix for this vulnerability
- Apply the latest Android security update available for the device
- For developers: Ensure the application or firmware uses a version of the media codec libraries that have been patched for this vulnerability
- Verify the Android version has the latest security patches applied by checking Settings > About Phone > Android Security Patch Level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20202 — 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-2022-20202 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