CVE-2020-11197
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 can occur when stream info update is called when total number of streams detected are zero while parsing TS clip with invalid data in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, 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 confidenceAn integer overflow vulnerability exists in the stream info update function of Qualcomm Snapdragon chipsets. The overflow occurs when the function is called while parsing a Transport Stream (TS) clip with invalid data when the total number of detected streams is zero. This can be exploited to achieve remote code execution or cause denial of service.
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
- 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 chipset modelOn Android devices, run 'cat /proc/cpuinfo' or check 'Settings > About Phone > Hardware' to find the processor/chipset name. On other embedded systems, check /proc/cpuinfo or boot logs for the Qualcomm chipset identifier.Affected if The chipset model matches any of the following: Apq8009, Apq8009w, Apq8017, Apq8037, Apq8053, Apq8064au, Apq8096au, or Aqt1000
-
Verify the vulnerability trigger condition existsDetermine if the device or application parses Transport Stream (TS) media files or streams. Check media player logs, application documentation, or network traffic for .ts file handling or MPEG-TS protocol processing.Affected if The device processes Transport Stream (TS) clips with potentially malformed or untrusted stream data, and the stream info update function is called when the detected stream count is zero
-
Confirm the firmware is unpatchedCheck the firmware or baseband version through 'Settings > About Phone > Build number' or by querying the modem/firmware version via AT commands or system properties (getprop ro.build.version.security_patch, getprop persist.sys.miui.build.version.twrp). Compare against any available vendor security bulletins.Affected if The device firmware does not contain the Qualcomm security patch for CVE-2020-11197 and remains on the original unpatched build for the affected chipset
You are affected if your device uses any of the listed Qualcomm chipsets (Apq8009, Apq8009w, Apq8017, Apq8037, Apq8053, Apq8064au, Apq8096au, or Aqt1000) and processes Transport Stream content without having received the vendor security patch.
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 vendor-supplied security patch from Qualcomm, which typically comes as a firmware or platform update. Device manufacturers should push available security updates to affected products promptly.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11197 — 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-11197 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