LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11308: Buffer overflow occurs when trying to convert ASCII string to Unicode string if the actual size is more tha...

Buffer overflow occurs when trying to convert ASCII string to Unicode string if the actual size is more than required in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a memory-safety flaw in Qualcomm Snapdragon software used across mobile, automotive, IoT, compute, connectivity, and audio products. A malformed or oversized string conversion can overflow memory. The public record does not provide severity, attack vector, impact, or affected OEM firmware details, so business urgency depends on where these chipsets appear in your fleet.

Executive priority

Prioritize discovery and vendor patch tracking, especially for managed mobile, automotive, IoT, and embedded assets. The public evidence is too incomplete to rank this as high urgency by itself, but the affected ecosystem is broad enough to justify ownership and follow-up.

Technical view

CVE-2020-11308 is a buffer overflow during ASCII-to-Unicode string conversion when the actual size exceeds the required size. Qualcomm lists many affected Snapdragon product families and components, but the provided sources do not specify CVSS, CWE, reachable interfaces, privileges required, exploit prerequisites, or fixed firmware versions.

Likely exposure

Organizations may be exposed through devices, vehicles, IoT equipment, or embedded systems using the listed Qualcomm Snapdragon components. Practical exposure depends on OEM firmware lineage and whether the vulnerable conversion path is present and reachable in deployed builds.

Exploitation context

The source bundle marks CISA KEV status as false and provides no cited evidence of active exploitation. It also does not describe public exploit availability, attacker access requirements, or real-world abuse. Treat exploitation status as unconfirmed, not absent.

Researcher notes

Key gaps are severity, affected firmware boundaries, trigger surface, privileges, impact, and fix identifiers. The affected product list is broad and truncated in the bundle, so validation should rely on Qualcomm/OEM bulletins and asset-level component mapping rather than product-family names alone.

Mitigation direction

  • Identify assets using affected Qualcomm Snapdragon components or OEM firmware branches.
  • Check Qualcomm and device OEM security guidance for fixed firmware availability.
  • Prioritize vendor firmware updates for externally exposed or safety-sensitive devices.
  • Apply compensating controls where firmware updates are unavailable.
  • Track OEM advisories because Qualcomm fixes often ship through device vendors.

Validation and detection

  • Inventory hardware models and map them to Qualcomm component identifiers.
  • Compare device firmware versions against Qualcomm and OEM security bulletins.
  • Confirm whether affected Snapdragon families appear in mobile, IoT, auto, or compute fleets.
  • Review vulnerability management records for OEM patch status and exceptions.
  • Document devices awaiting vendor guidance or unsupported firmware.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-11308 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & MusicAPQ8009, AQT1000, AR8031, AR8035, AR8151, CSRA6620, CSRA6640, CSRB31024, FSM10055, FSM10056, MDM9250, MDM9655, PM3003A, PM4125, PM4250, PM456, PM6125, PM6150, PM6150A, PM6150L, PM6250, PM6350, PM640A, PM640L, PM640P, PM660, PM660A, PM660L, PM670, PM670A, PM670L, PM7150A, PM7150L, PM7250, PM7250B, PM7350C, PM8004, PM8005, PM8008, PM8009, PM8150, PM8150A, PM8150B, PM8150C, PM8150L, PM8250, PM8350, PM8350B, PM8350BH, PM8350BHS, PM8350C, PM855, PM855B, PM855L, PM855P, PM8916, PM8998, PMC1000H, PMD9655, PME605, PMI632, PMI8998, PMK7350, PMK8002, PMK8003, PMK8350, PMM6155AU, PMM8155AU, PMM8195AU, PMM855AU, PMR525, PMR735A, PMR735B, PMX24, PMX50, PMX55, QAT3514, QAT3516, QAT3518, QAT3519, QAT3522, QAT3550, QAT3555, QAT5515, QAT5516, QAT5522, QAT5533, QAT5568, QBT1000, QBT1500, QBT2000, QCA6174A, QCA6310, QCA6320, QCA6335, QCA6390, QCA6391, QCA6420, QCA6421, QCA6426, QCA6430, QCA6431, QCA6436, QCA6564, QCA6564A, QCA6564AU, QCA6574, QCA6574A, QCA6574AU, QCA6584AU, QCA6595, QCA6595AU, QCA6696, QCA8337, ...[truncated*]Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.