CVE-2020-0283
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 · uneditedThere is a possible out of bounds write due to a missing bounds check.Product: AndroidVersions: Android SoCAndroid ID: A-163008257
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 · moderate confidenceA missing bounds check in Android SoC allows an out of bounds write, leading to memory corruption. This is a critical memory safety vulnerability in low-level firmware or drivers running on the System-on-Chip, potentially allowing arbitrary code execution or denial of service.
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 dataall versionsCVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Identify the SoC chipset modelCheck device specifications or run 'getprop ro.hardware' or 'cat /proc/cpuinfo' to identify the SoC vendor and model (e.g., Qualcomm, MediaTek, Samsung Exynos, HiSilicon)Affected if The device uses a SoC model that received this vulnerability fix from its manufacturer
-
Check Android security patch levelGo to Settings > About Phone > Build Number or run 'getprop ro.build.version.security_patch' to see the installed security patch dateAffected if The security patch level is earlier than the month the CVE fix was released for the specific SoC vendor
-
Verify if the vulnerable driver component is presentCheck for the presence of the affected low-level media or graphics driver module by examining /system/lib/hw/ or /vendor/lib/hw/ directories for SoC-specific driver librariesAffected if Vulnerable SoC-specific driver binaries are present and have not been patched by the vendor
-
Check vendor firmware version if accessibleFor rooted devices, examine the bootloader or baseband version via 'getprop' commands (e.g., ro.bootloader, ro.baseband) or check /vendor/firmware/ for the base firmware versionAffected if The firmware version predates the vendor's patched release for this CVE
-
Confirm SoC vendor security advisory statusLook up whether the device manufacturer's security advisory or the SoC vendor has published a fix for CVE-2020-0283 affecting this specific chipsetAffected if No vendor acknowledgment or patch is available for the identified SoC model
A device is affected if it uses a vulnerable SoC chipset model and has not received the vendor-specific firmware or security patch that addresses the missing bounds check in the low-level SoC driver.
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 patches from the SoC vendor (chipset manufacturer) as they become available; this is a firmware-level fix that requires updating the SoC firmware or receiving patched Android security bulletins.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,384.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0283 — 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-0283 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