LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11114: u'Bluetooth devices does not properly restrict the L2CAP payload length allowing users in radio range to ca...

u'Bluetooth devices does not properly restrict the L2CAP payload length allowing users in radio range to cause a buffer overflow via a crafted Link Layer packet(Equivalent to CVE-2019-17060,CVE-2019-17061 and CVE-2019-17517 in Sweyntooth paper)' in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music in AR9344

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-11114 is a Bluetooth buffer overflow issue in listed Qualcomm Snapdragon product lines using AR9344. An attacker must be within radio range and able to send a crafted Bluetooth Link Layer packet. The source bundle does not provide a CVSS score, patch details, or evidence of active exploitation.

Executive priority

Treat this as an exposure-discovery and vendor-remediation task, not an internet-wide emergency based on available evidence. Priority rises for high-value facilities or devices where nearby attackers could access Bluetooth radio range.

Technical view

The issue is improper restriction of L2CAP payload length, allowing a buffer overflow through a crafted Link Layer packet. Qualcomm lists affected Snapdragon Compute, Consumer IoT, Industrial IoT, IoT, Mobile, and Voice & Music products in AR9344. The record says it is equivalent to SweynTooth-paper CVEs CVE-2019-17060, CVE-2019-17061, and CVE-2019-17517.

Likely exposure

Exposure is limited to devices using the affected Qualcomm AR9344 Bluetooth implementation within the listed Snapdragon product families. Practical risk depends on deployed device models, firmware lineage, Bluetooth enablement, and whether OEMs incorporated Qualcomm guidance from the October 2020 bulletin.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. The described attacker position is local radio range, not internet remote. The bundle does not describe exploit reliability, crash impact, code execution, or public exploit availability.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or explicit fix details are included in the source bundle. The strongest technical anchor is the L2CAP payload-length overflow description and Qualcomm’s October 2020 bulletin reference. Avoid assuming impact beyond buffer overflow without vendor detail.

Mitigation direction

  • Review Qualcomm October 2020 bulletin and applicable OEM advisories.
  • Inventory devices using Qualcomm AR9344 Bluetooth components.
  • Apply OEM firmware or software updates when vendor guidance identifies them.
  • Restrict Bluetooth use on affected assets where business operations allow.
  • Prioritize unmanaged IoT, mobile, and voice/music devices for vendor status checks.

Validation and detection

  • Map deployed device models to Qualcomm AR9344 or affected Snapdragon lines.
  • Compare device firmware against Qualcomm and OEM October 2020 remediation guidance.
  • Confirm whether Bluetooth is enabled on potentially affected assets.
  • Check CISA KEV and vendor advisories before declaring active exploitation.
  • Document unsupported devices needing replacement or compensating controls.
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-11114 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 Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & MusicAR9344Listed
Weakness

CWE details

No CWE listed

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