CVE-2020-11306
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 · uneditedPossible integer overflow in RPMB counter due to lack of length check on user provided data in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking
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 confidenceInteger overflow vulnerability in the RPMB (Replay Protected Memory Block) counter implementation within Qualcomm Snapdragon chipsets. The lack of proper length validation on user-provided data allows an attacker to trigger an overflow condition in the counter, potentially bypassing replay protection security controls and compromising secure storage functionality.
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 versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 chipset modelCheck the device documentation, system information, or boot logs for the Qualcomm chipset identifier (e.g., Aqt1000, Ar8035, Qca6390, Qca6391, Qca6420, Qca6421, Qca6426, Qca6430). On Linux systems, try 'dmesg', '/proc/cpuinfo', or check bootloader output.Affected if The chipset model matches any of the listed affected models (Aqt1000, Ar8035, Qca6390, Qca6391, Qca6420, Qca6421, Qca6426, Qca6430).
-
Confirm RPMB functionality is in useVerify whether the device implements RPMB (Replay Protected Memory Block) secure storage. Check for RPMB-related kernel modules, device nodes (e.g., /dev/rpmb0), or firmware that accesses secure storage partitions.Affected if RPMB secure storage functionality is enabled or accessible on the device.
-
Check for user-accessible RPMB interfacesInspect the system for exposed RPMB programming interfaces, APIs, or debug features that accept user-provided data lengths. Look for any custom or vendor-specific tools that interact with the RPMB counter.Affected if There are exposed interfaces or tools that allow user-controlled input to reach the RPMB counter implementation.
-
Review firmware version for referenceIf available, retrieve the firmware version of the affected chipset for documentation purposes. Note that all versions are affected per the advisory.Affected if Any firmware version is present on the listed affected chipsets.
If the device uses any of the affected Qualcomm chipset models (Aqt1000, Ar8035, Qca6390, Qca6391, Qca6420, Qca6421, Qca6426, Qca6430) with RPMB functionality enabled, the environment is 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 Qualcomm firmware/hardware updates distributed through device manufacturers; for devices no longer receiving updates, consider compensating controls such as restricting access to RPMB interfaces and monitoring for anomalous storage access patterns.
- Consultation16.0 h
- Implementation40.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 $25,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11306 — 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-11306 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