LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11206: Possible buffer overflow in Fastrpc while handling received parameters due to lack of validation on input p...

Possible buffer overflow in Fastrpc while handling received parameters due to lack of validation on input parameters' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in APQ8098, MSM8998, QCM4290, QCM6125, QCS410, QCS4290, QCS610, QCS6125, QSM8250, QSM8350, SA6145P, SA6150P, SA6155, SA6155P, SA8150P, SA8155, SA8155P, SA8195P, SC7180, SDA640, SDA660, SDA845, SDA855, SDM640, SDM660, SDM830, SDM845, SDM850, SDX50M, SDX55, SDX55M, SM4250, SM4250P, SM6115, SM6115P, SM6125, SM6150, SM6150P, SM6250, SM6250P, SM6350, SM7125, SM7150, SM7150P, SM7225, SM7250, SM7250P, SM8150, SM8150P, SM8250, SM8350, SM8350P, SXR2130, SXR2130P

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Qualcomm Snapdragon FastRPC input-validation flaw that may cause a buffer overflow when parameters are handled. It affects multiple Snapdragon product lines used in mobile, automotive, compute, and IoT devices. The source bundle does not provide CVSS or active exploitation evidence, so urgency depends on whether your fleet uses listed chips and has vendor firmware updates available.

Executive priority

Treat this as an asset-exposure and vendor-update priority, not as a confirmed breach indicator. Because affected Snapdragon platforms are broad and often embedded, unsupported devices may create long-lived risk even without public active-exploitation evidence.

Technical view

CVE-2020-11206 is described as a possible buffer overflow in FastRPC caused by insufficient validation of received input parameters. Affected silicon includes many APQ, MSM, QCM, QCS, SA, SC, SDA, SDM, SDX, SM, and SXR Snapdragon platforms. The bundle cites Qualcomm's November 2020 bulletin and Check Point research, but provides no CVSS, CWE, exploit mechanics, or patch details.

Likely exposure

Exposure is most likely through devices containing the listed Qualcomm Snapdragon platforms, especially Android, embedded, automotive, IoT, or compute products whose firmware includes vulnerable FastRPC components. Product-level exposure requires OEM firmware confirmation.

Exploitation context

The provided bundle does not show CISA KEV listing or confirmed active exploitation. Check Point research links indicate public security research around Qualcomm DSP issues, but this bundle does not prove this CVE is exploited in the wild.

Researcher notes

The bundle supports only a general memory-corruption characterization: possible FastRPC buffer overflow from missing parameter validation. It does not provide CVSS, CWE, privilege boundary, affected firmware versions, exploitability prerequisites, or fixed build identifiers. Avoid assuming device impact without OEM mapping.

Mitigation direction

  • Identify devices using affected Snapdragon chipsets listed in the CVE record.
  • Check Qualcomm and OEM advisories for firmware containing the November 2020 security fixes.
  • Prioritize managed mobile, automotive, IoT, and embedded devices with exposed update gaps.
  • Apply vendor firmware or OS updates through approved device-management channels.
  • If no update exists, request OEM guidance and document residual risk.

Validation and detection

  • Inventory hardware models and map them to Qualcomm chipset identifiers.
  • Confirm each model's firmware security patch level with the OEM or device-management platform.
  • Review Qualcomm November 2020 bulletin applicability for the chipset family.
  • Check whether compensating controls or isolation exist for unpatchable embedded devices.
  • Track vendor support status for end-of-life devices using listed platforms.
Prepared
Confidence
medium
Sources
5

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-11206 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
4Source 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 Consumer IOT, Snapdragon Industrial IOT, Snapdragon MobileAPQ8098, MSM8998, QCM4290, QCM6125, QCS410, QCS4290, QCS610, QCS6125, QSM8250, QSM8350, SA6145P, SA6150P, SA6155, SA6155P, SA8150P, SA8155, SA8155P, SA8195P, SC7180, SDA640, SDA660, SDA845, SDA855, SDM640, SDM660, SDM830, SDM845, SDM850, SDX50M, SDX55, SDX55M, SM4250, SM4250P, SM6115, SM6115P, SM6125, SM6150, SM6150P, SM6250, SM6250P, SM6350, SM7125, SM7150, SM7150P, SM7225, SM7250, SM7250P, SM8150, SM8150P, SM8250, SM8350, SM8350P, SXR2130, SXR2130PListed
Weakness

CWE details

No CWE listed

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