LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11222: Buffer over read while processing MT SMS with maximum length due to improper length check in Snapdragon Aut...

Buffer over read while processing MT SMS with maximum length due to improper length check in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-11222 is a Qualcomm Snapdragon issue where specially sized mobile-terminated SMS processing can read past a buffer. The main business concern is device reliability and potential exposure across products built on affected Snapdragon components. The public bundle does not provide CVSS, a named patch version, or evidence of active exploitation.

Executive priority

Treat this as an inventory and vendor-update tracking item, not an emergency based on current evidence. Priority should rise where affected devices are unmanaged, unsupported, safety-sensitive, or deployed in high-volume SMS-reachable environments.

Technical view

The flaw is described as a buffer over-read caused by an improper length check while processing maximum-length MT SMS. Qualcomm lists broad Snapdragon Auto, Compute, Connectivity, Consumer/Industrial IoT, IoT, and Mobile product families and many component identifiers. No CWE, CVSS vector, exploit details, or complete remediation details are included in the supplied data.

Likely exposure

Exposure is most likely in phones, IoT, automotive, compute, or connectivity devices using the listed Qualcomm Snapdragon components. Because OEMs integrate Qualcomm firmware differently, vulnerability managers should map exact chipsets and vendor firmware levels rather than assuming every Snapdragon-branded device is affected.

Exploitation context

The source bundle marks this CVE as not in KEV and provides no cited evidence of active exploitation. The available description implies the attack surface involves inbound SMS handling, but the supplied sources do not establish exploitability, required proximity, privileges, or user interaction.

Researcher notes

The public bundle is sparse: it names a buffer over-read in MT SMS processing and lists broad Qualcomm product families, but lacks CVSS, CWE, exploit preconditions, and precise fixed versions. Avoid over-scoping without OEM-specific firmware evidence.

Mitigation direction

  • Check Qualcomm's March 2021 security bulletin for vendor guidance on this CVE.
  • Request OEM firmware or security patch confirmation for affected device models.
  • Prioritize updates for mobile, IoT, automotive, and remote-field devices using listed chipsets.
  • Retire or isolate unsupported devices that cannot receive OEM security updates.
  • Monitor vendor advisories for device-specific remediation status.

Validation and detection

  • Inventory deployed devices and map them to Qualcomm component identifiers.
  • Confirm whether each OEM advisory references CVE-2020-11222 or the March 2021 Qualcomm bulletin.
  • Record firmware, baseband, modem, and Android security patch levels where applicable.
  • Review fleet telemetry for SMS-handling crashes or unexplained modem resets.
  • Document unsupported affected devices as residual risk.
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-11222 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 IoT, Snapdragon MobileAPQ8017, APQ8053, AQT1000, AR8035, CSRB31024, MSM8917, MSM8920, MSM8940, MSM8953, MSM8976, MSM8976SG, PM3003A, PM4125, PM4250, PM456, PM6125, PM6150, PM6150A, PM6150L, PM6250, PM640A, PM640L, PM640P, PM660, PM660A, PM660L, PM7150A, PM7150L, PM7250, PM7250B, PM8004, PM8005, PM8008, PM8009, PM8150, PM8150A, PM8150B, PM8150C, PM8150L, PM8250, PM855, PM855A, PM855B, PM855L, PM855P, PM8937, PM8940, PM8952, PM8953, PM8956, PM8998, PMC1000H, PMI632, PMI8937, PMI8940, PMI8952, PMI8998, PMK8002, PMM855AU, PMR525, PMR735A, PMX24, PMX50, PMX55, QAT3514, QAT3516, QAT3518, QAT3519, QAT3522, QAT3550, QAT3555, QAT5515, QAT5516, QAT5522, QAT5533, QBT1500, QBT2000, QCA6174A, QCA6390, QCA6391, QCA6420, QCA6421, QCA6426, QCA6430, QCA6431, QCA6436, QCA6564AU, QCA6574A, QCA6574AU, QCA6584AU, QCA6595AU, QCA6696, QCA8337, QCA9377, QCA9379, QCM2290, QCM4290, QCM6125, QCS2290, QCS410, QCS4290, QCS610, QCS6125, QDM2301, QDM2302, QDM2305, QDM2307, QDM2308, QDM2310, QDM3301, QDM5620, QDM5621, QDM5650, QDM5652, QDM5670, Q ...[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.