# CVE-2020-3615: Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

> A flaw in Qualcomm Snapdragon firmware allows rogue peers to drop valid deauth frames, causing denial of service when RMF is enabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8xmf-9w6j-h6fw

## What is CVE-2020-3615?

CVE-2020-3615 is a critical denial of service vulnerability in Qualcomm Apq8009 Firmware, published on 2 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Valid deauth/disassoc frames is dropped in case if RMF is enabled and some rouge peer keep on sending rogue deauth/disassoc frames due to improper enum values used to check the frame subtype in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in APQ8009, APQ8053, APQ8096AU, MDM9150, MDM9206, MDM9207C, MDM9607, MDM9650, MSM8996AU, QCA6174A, QCA6574AU, QCA9377, QCA9379, QCN7605, QCS605, SC8180X, SDM630, SDM636, SDM660, SDM845, SDX20, SDX24, SDX55, SM8150, SXR1130

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2020-3615?

It affects 25 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9207c Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca9377 Firmware, Qualcomm Qca9379 Firmware, Qualcomm Qcn7605 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sc8180x Firmware, Qualcomm Sdm630 Firmware, Qualcomm Sdm636 Firmware, Qualcomm Sdm660 Firmware, Qualcomm Sdm845 Firmware and 5 more.

## How do I fix CVE-2020-3615?

No fix has been published for CVE-2020-3615 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-3615 being exploited?

There is no known exploitation of CVE-2020-3615 in the wild and no public exploit code.

## Other vulnerabilities in Qualcomm Apq8009 Firmware

- [CVE-2021-1905](https://insights.sbomify.com/CVE-2021-1905/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11261](https://insights.sbomify.com/CVE-2020-11261/): Qualcomm Multiple Chipsets Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2021-1906](https://insights.sbomify.com/CVE-2021-1906/): Qualcomm Multiple Chipsets Detection of Error Condition Without Action (medium 6.2, exploited in the wild)
- [CVE-2022-40510](https://insights.sbomify.com/CVE-2022-40510/): Buffer copy without checking size of input in Audio. (critical 9.8)
- [CVE-2022-22088](https://insights.sbomify.com/CVE-2022-22088/): Integer Overflow to Buffer Overflow in Bluetooth HOST (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-3615 and fix it if it is affected.

What it is: CVE-2020-3615 is a critical denial of service vulnerability in Qualcomm Apq8009 Firmware, published on 2 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-3615 in the wild and no public exploit code.

Affected product: Qualcomm Apq8009 Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-3615/ (Markdown: https://insights.sbomify.com/CVE-2020-3615/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-3615
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-3615
- OSV: https://osv.dev/vulnerability/CVE-2020-3615

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-3615/
Summaries are generated and may contain mistakes; the official description above is the record.