CVE-2020-0339
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-162980705
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 · low confidenceThis is an out-of-bounds read vulnerability in Android System-on-Chip (SoC) components caused by a missing bounds check. The flaw allows a local attacker to potentially read sensitive data from memory locations outside the intended buffer boundary, which could lead to information disclosure or assist in further exploitation.
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 the Android security patch levelGo to Settings > About Phone > Security Patch Level (or Settings > System > Security > Security Patch Level on newer Android versions). Record the date shown (e.g., October 1, 2020 or later).Affected if The security patch level is earlier than October 2020, meaning the CVE has not been addressed.
-
Identify the SoC vendor and modelGo to Settings > About Phone > Model/Hardware (or use the command 'cat /proc/cpuinfo' via ADB shell). Look for the chipset manufacturer such as Qualcomm (Snapdragon), MediaTek, Samsung Exynos, HiSilicon (Huawei), or other SoC vendors.Affected if The device uses an affected SoC from any vendor and is running an unpatched security level.
-
Verify the device is receiving active security updatesCheck with your device manufacturer (Samsung, Google Pixel, LG, etc.) or mobile carrier if the device is still listed as supported for monthly security updates. Check the manufacturer website for the last update date.Affected if The device is no longer supported by the manufacturer and has not received the October 2020 or later security patch.
-
For enterprise-managed devices, check the MDM/EMM patch statusIf the device is enrolled in Mobile Device Management (MDM) or Enterprise Mobility Management (EMM) such as Microsoft Intune, VMware Workspace ONE, or Jamf, query the security patch compliance report. Look for the 'Security Patch Level' attribute.Affected if The MDM reports a security patch level earlier than October 2020, or the device is marked as non-compliant with organizational patch policies.
The device is affected if its Android Security Patch Level is earlier than October 2020, or if it uses an unpatched SoC firmware from any 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 the latest Android security patch level (SVR level or vendor-specific SoC patch) from your device or SoC vendor. Organizations should inventory affected Android devices and ensure timely application of monthly security updates.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0339 — 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-0339 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