CVE-2021-0406
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 cameraisp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Product: Android; Versions: Android-10, Android-11; Patch ID: ALPS05471418.
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 bounds check is missing in the cameraisp component of Android, allowing an out-of-bounds write vulnerability. This enables local privilege escalation from the attacker's current privilege level to System execution privileges without requiring user interaction.
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= 10.0= 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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.
-
Check Android versionRun 'getprop ro.build.version.release' or check Settings > About Phone > Android version. Compare the result to the affected versions 10.0 and 11.0.Affected if The device is running Android 10.0 or Android 11.0 specifically.
-
Confirm cameraisp component presenceCheck if the device has a camera subsystem by looking for cameraisp-related processes or kernel modules. On Android, you can grep system logs or check /proc for camera-related processes: 'ps -A | grep -i camera' or check /vendor/lib for camera ISP libraries.Affected if The device has a camera subsystem with cameraisp component loaded (most Android 10/11 devices with camera hardware).
-
Verify patch ALPS05471418 integrationCheck the security patch level via 'getprop ro.build.version.security_patch' or check the build fingerprint with 'getprop ro.build.fingerprint'. Compare against the patch date for ALPS05471418 or look for the specific patch identifier in system properties if exposed.Affected if The device security patch level predates the ALPS05471418 fix, or the patch is not listed in the applied security updates.
A device is affected if it runs Android 10.0 or 11.0, contains the cameraisp component, and has not received the ALPS05471418 bounds check 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.
From vendor dataApply the official patch ALPS05471418 which adds proper bounds checking to the cameraisp component. Given this is a kernel/driver-level fix in Android-10 and Android-11, ensure the patch is integrated into the device's firmware update cycle.
- Consultation6.0 h
- Implementation12.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0406 — 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-0406 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