dbcve.org
Agatti FirmwareOperating system · Qualcomm

CVE-2020-3704

HIGH · 7.5 CVSS v3.1 Published 2020-11-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
u'While processing invalid connection request PDU which is nonstandard (interval or timeout is 0) from central device may lead peripheral system enter into dead lock state.(This CVE is equivalent to InvalidConnectionRequest(CVE-2019-19193) mentioned in sweyntooth paper)' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in Agatti, APQ8009, APQ8017, APQ8053, AR9344, Bitra, IPQ5018, Kamorta, MDM9607, MDM9640, MDM9650, MSM8996AU, Nicobar, QCA6174A, QCA6390, QCA6574AU, QCA9377, QCA9886, QCM6125, QCN7605, QCS404, QCS405, QCS605, QCS610, QRB5165, Rennell, SA415M, SA515M, Saipan, SC7180, SC8180X, SDA845, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a Bluetooth Low Energy (BLE) stack vulnerability in Qualcomm Snapdragon chipsets. When a central device sends a malformed connection request PDU with invalid parameters (interval or timeout set to 0), the peripheral device's BLE stack enters a deadlock state. This is equivalent to the InvalidConnectionRequest vulnerability (CVE-2019-19193) documented in the Sweyntooth paper, indicating a protocol handling flaw in the BLE connection state machine.

MitigationThis is a firmware-level vulnerability requiring a patch from Qualcomm that device manufacturers must integrate and deploy. Users should check with their device OEMs for available firmware updates addressing this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Agatti FirmwareOperating system
Affected:all versions
Apq8009 FirmwareOperating system
Affected:all versions
Apq8017 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Ar9344 FirmwareOperating system
Affected:all versions
Bitra FirmwareOperating system
Affected:all versions
Ipq5018 FirmwareOperating system
Affected:all versions
Kamorta FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the chipset model
    Determine the specific Qualcomm chipset or SoC model used in the device (check device documentation, system information, or FCC ID filings)
    Affected if The chipset matches one of the following: Agatti, Apq8009, Apq8017, Apq8053, Ar9344, Bitra, Ipq5018, or Kamorta
  2. Confirm BLE functionality is in use
    Check whether Bluetooth Low Energy (BLE) is enabled and actively configured on the device
    Affected if BLE is enabled and the device supports BLE peripheral or observer roles
  3. Check BLE peripheral role configuration
    Inspect whether the device is configured to accept BLE connections as a peripheral (GATT server, advertisement responder)
    Affected if The device acts as a BLE peripheral that accepts connection requests from central devices
  4. Verify device is acting as BLE server
    Determine if the device runs BLE services or profiles that accept incoming connection requests
    Affected if The device exposes BLE GATT services or acts as a BLE server accepting connections
  5. Review vendor firmware version
    Check the installed firmware version from the device settings or system logs
    Affected if All firmware versions for the listed chipsets are affected; no version is exempt

The device is affected if it uses any of the listed Qualcomm chipsets (Agatti, Apq8009, Apq8017, Apq8053, Ar9344, Bitra, Ipq5018, Kamorta) and has BLE peripheral functionality enabled, as all firmware versions for these chipsets contain the vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

This is a firmware-level vulnerability requiring a patch from Qualcomm that device manufacturers must integrate and deploy. Users should check with their device OEMs for available firmware updates addressing this vulnerability.

Fix this in Agatti Firmware Scoped from the published advisory
  • Consultation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,184.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-3704 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data