CVE-2020-0376
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 read due to a missing bounds check.Product: AndroidVersions: Android SoCAndroid ID: A-163003156
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 confidenceOut of bounds read vulnerability in Android System-on-Chip (SoC) components due to a missing bounds check. This allows reading memory beyond allocated buffer boundaries, potentially exposing sensitive data or enabling further exploitation. The vulnerability has critical severity (CVSS 9.1) indicating network-exploitable with no authentication required.
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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Any version of Android is installed (all versions affected per vendor)
-
Check Android security patch levelGo to Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if Security patch level is earlier than the vendor-provided patch date for CVE-2020-0376 (no patch date specified in provided data)
-
Identify SoC vendor and modelRun 'getprop ro.hardware' or 'getprop ro.soc.model' via ADB, or check Settings > About Phone > SoC detailsAffected if Device uses an affected SoC (specific SoC models not enumerated in provided data)
-
Check SoC firmware version if accessibleRun 'getprop ro.vendor.[soc_vendor].fw.version' or check vendor-specific diagnostic menus; consult SoC vendor documentationAffected if SoC firmware version is unpatched for this vulnerability (specific version ranges not provided)
-
Assess network exposure of SoC-related servicesReview running network services via 'netstat -an' or 'ss -tulpn' and check for exposed SoC-related interfaces (e.g., radio, baseband, media services)Affected if Network-facing services utilizing vulnerable SoC components are enabled and accessible
Device is affected if running any Android version with a security patch level predating the CVE-2020-0376 fix, regardless of specific SoC, since all Android versions are listed as affected.
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 available security patches from Android and SoC vendors. Until a patch is available, minimize exposure by restricting network-facing services and monitoring for indicators of compromise.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0376 — 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-0376 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