LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11207: Buffer overflow in LibFastCV library due to improper size checks with respect to buffer length' in Snapdrag...

Buffer overflow in LibFastCV library due to improper size checks with respect to buffer length' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in APQ8052, APQ8056, APQ8076, APQ8096, APQ8096SG, APQ8098, MDM9655, MSM8952, MSM8956, MSM8976, MSM8976SG, MSM8996, MSM8996SG, MSM8998, QCM4290, QCM6125, QCS410, QCS4290, QCS610, QCS6125, QSM8250, 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, SXR2130, SXR2130P

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-11207 is a Qualcomm Snapdragon LibFastCV buffer overflow caused by insufficient buffer length checks. It affects many Snapdragon Auto, Compute, IoT, Industrial IoT, and Mobile chipsets. The sources do not provide CVSS, business impact, or confirmed in-the-wild exploitation, so urgency depends on whether affected Qualcomm-based devices are in use.

Executive priority

Medium operational priority until exposure is confirmed. Escalate if affected Snapdragon devices support critical business, automotive, industrial, or managed mobile functions and cannot receive OEM updates.

Technical view

The CVE describes a buffer overflow in Qualcomm LibFastCV tied to improper size checks against buffer length. Qualcomm’s affected list spans numerous APQ, MDM, MSM, QCM, QCS, SA, SC, SDA, SDM, SDX, SM, and SXR platforms. Public details in the bundle do not define attack prerequisites, privileges, impact, or patch identifiers.

Likely exposure

Exposure is most likely in products or embedded systems using the listed Snapdragon platforms, including mobile, automotive, compute, and IoT devices. Asset teams should map device models to Qualcomm chipsets and OEM firmware levels rather than assuming exposure from software package names alone.

Exploitation context

The bundle links this CVE to public Qualcomm and Check Point research references, but it does not state active exploitation. The CVE is not marked KEV. Treat public awareness as a research and patch-management signal, not proof of exploitation in the wild.

Researcher notes

Evidence is incomplete for exploitability details. The CVE gives the vulnerable library class and affected platforms, but not attack vector, privilege requirements, reachable APIs, or fixed component versions. Avoid assuming exploitability on every listed device without vendor firmware context.

Mitigation direction

  • Review Qualcomm’s November 2020 security bulletin for vendor guidance.
  • Apply OEM firmware or security updates that include Qualcomm’s fix.
  • Inventory devices using the listed Snapdragon platforms.
  • Ask vendors for explicit CVE-2020-11207 remediation status.
  • Prioritize externally managed, safety-critical, and long-lived embedded assets.

Validation and detection

  • Map device models to Qualcomm chipset identifiers in the affected list.
  • Verify firmware or Android security patch levels with each OEM.
  • Check vendor advisories for CVE-2020-11207 coverage.
  • Document devices awaiting OEM fixes or unsupported firmware.
  • Monitor Qualcomm and OEM bulletins for updated remediation guidance.
Prepared
Confidence
medium
Sources
5

Public sources used

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-11207 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon MobileAPQ8052, APQ8056, APQ8076, APQ8096, APQ8096SG, APQ8098, MDM9655, MSM8952, MSM8956, MSM8976, MSM8976SG, MSM8996, MSM8996SG, MSM8998, QCM4290, QCM6125, QCS410, QCS4290, QCS610, QCS6125, QSM8250, 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, 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.