CVE-2020-0230
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 an incorrect bounds check. Product: AndroidVersions: Android SoCAndroid ID: A-156337262
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 confidenceThis is a critical out-of-bounds write vulnerability in Android System-on-a-Chip (SoC) firmware caused by an incorrect bounds check. The vulnerability allows writing data beyond allocated memory boundaries, potentially leading to memory corruption, privilege escalation, or remote code execution.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify the SoC chipset vendorCheck Settings > About Phone > CPU/Processor or use 'cat /proc/cpuinfo' to identify whether the device uses Qualcomm, MediaTek, or another chipset. This vulnerability exists in SoC firmware, not the Android OS itself.Affected if The device uses a vulnerable SoC chipset that has not received firmware updates from the chipset vendor.
-
Check the Android security patch levelGo to Settings > About Phone > Android security patch level. This shows when the device last received security updates from the OEM.Affected if The security patch level is earlier than the month when the SoC vendor released the CVE-2020-0230 fix (typically requires OEM firmware update).
-
Check the baseband/modem versionGo to Settings > About Phone > Baseband version or use 'getprop gsm.version.baseband' via ADB. This often contains SoC firmware version information.Affected if The baseband version corresponds to an unpatched SoC firmware build.
-
Check the bootloader versionBoot the device into fastboot mode (power + volume down) and run 'fastboot getvar all' or check Settings > Developer Options > Bootloader version.Affected if The bootloader version indicates firmware that predates the CVE-2020-0230 patch from the SoC vendor.
-
Verify OEM support statusCheck the device manufacturer's security advisory or support pages for mention of CVE-2020-0230 and confirm your specific device model has received the corresponding firmware update.Affected if The OEM has not published a security update addressing this CVE for your exact device model.
A user is affected if their device runs SoC firmware without the CVE-2020-0230 fix, which manifests as an older Android security patch level or unpatched baseband/bootloader version from the chipset vendor.
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 device manufacturer's firmware updates. This is a SoC-level vulnerability requiring updates from the chipset vendor (Qualcomm, MediaTek, etc.) propagated through the device OEM's ROM updates.
- Consultation8.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 $6,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0230 — 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-0230 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