CVE-2020-11294
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 · uneditedOut of bound write in logger due to prefix size is not validated while prepended to logging string in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
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 · high confidenceMemory corruption vulnerability in Qualcomm Snapdragon processors' logger component where prefix size is not validated before being prepended to a logging string, leading to an out-of-bounds write. This is a classic buffer overflow in the logging subsystem that can allow memory corruption.
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 processor and firmware componentsDetermine if the system uses a Qualcomm Snapdragon processor and which firmware components are present. Check system documentation, device specifications, or /proc/cpuinfo for Qualcomm Snapdragon identifiers. For embedded systems, check the bootloader or firmware inventory for presence of Ar8035, Pm215, Pm3003a, Pm6125, Pm6150, Pm6150a, Pm6150l, or Pm6350 firmware modules.Affected if The device contains any of the listed Qualcomm firmware components (Ar8035, Pm215, Pm3003a, Pm6125, Pm6150, Pm6150a, Pm6150l, Pm6350).
-
Verify logger component is activeDetermine whether the logging subsystem is enabled on the device. This may be checked via system configuration files, kernel parameters, or runtime service status depending on the device architecture. Look for logger, logd, or diagnostic logging services.Affected if The logger component is enabled and running on the system.
-
Confirm firmware version is unpatchedQuery the firmware version of the affected Qualcomm components through vendor-specific tools, diagnostic interfaces, or system information APIs. Compare against the latest vendor firmware releases.Affected if The firmware version has not received the vendor security patch for this CVE (note: all versions listed are affected until patched).
A system is affected if it contains any of the listed Qualcomm firmware components (Ar8035, Pm215, Pm3003a, Pm6125, Pm6150, Pm6150a, Pm6150l, Pm6350) with the logger feature enabled and without the CVE-specific vendor patch applied.
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 vendor firmware patches from Qualcomm to affected Snapdragon chipsets; downstream device manufacturers must integrate these patches and deliver OTA updates to end-user devices.
- Consultation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11294 — 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-11294 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