CVE-2021-0563
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 ih264e_fmt_conv_422i_to_420sp of ih264e_fmt_conv.c, there is a possible out of bounds read due to a heap buffer overflow. 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-172908358
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 confidenceHeap buffer overflow in ih264e_fmt_conv_422i_to_420sp function in the H.264 encoder allows out-of-bounds read during YUV 422i to 420sp format conversion, enabling local information disclosure without user interaction or additional 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
- 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 device or system Android version via Settings > About Phone > Android version, or run 'getprop ro.build.version.release' in ADB shellAffected if Android version equals 11.0 exactly (not 10, 12, or later)
-
Identify H.264 encoder usageCheck if the device or application uses the media framework H.264 encoder component. Review logs for 'ih264e' or H.264 encoding operations, or inspect installed media/camera applications that perform video encodingAffected if H.264 video encoding is performed using the affected media framework encoder
-
Confirm YUV 422i to 420sp conversion is in useMonitor or inspect media pipeline for YUV 422i to 420sp format conversion operations during video encoding. This is typically used when processing certain camera capture or video input formatsAffected if Video encoding involves YUV 422i to 420sp format conversion in the encoder pipeline
-
Check for vulnerable media framework componentInspect the media framework libraries (libmedia.so, libstagefright.so, or vendor-specific encoder libraries) for the presence of the ih264e_fmt_conv_422i_to_420sp function in the H.264 encoderAffected if The ih264e_fmt_conv_422i_to_420sp function exists in the installed media framework and is callable during encoding
A user is affected if the device runs Android 11.0 and performs H.264 encoding that involves YUV 422i to 420sp format conversion through the vulnerable function in the media framework.
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 security updates for Android-11 that address this vulnerability in the media framework H.264 encoder component.
- 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-2021-0563 — 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-2021-0563 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