# CVE-2020-3700: Information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

> A missing bounds check in the Qualcomm WiFi driver allows local attackers to read out-of-bounds memory, leading to information disclosure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** 2389239, A-153345156, ASB-A-153345156, GHSA-rc74-rr58-4f4g

## What is CVE-2020-3700?

CVE-2020-3700 is a high-severity vulnerability in Qualcomm Apq8053 Firmware, published on 30 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Possible out of bounds read due to a missing bounds check and could lead to local information disclosure in the wifi driver with no additional execution privileges needed in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in APQ8053, APQ8096AU, IPQ4019, IPQ8064, IPQ8074, MDM9607, MSM8909W, MSM8996AU, QCA6574AU, QCA9531, QCA9558, QCA9980, SC8180X, SDM439, SDX55, SM8150, SM8250, SXR2130

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 18 products.


Products: Qualcomm Apq8053 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Ipq4019 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Ipq8074 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca9531 Firmware, Qualcomm Qca9558 Firmware, Qualcomm Qca9980 Firmware, Qualcomm Sc8180x Firmware, Qualcomm Sdm439 Firmware, Qualcomm Sdx55 Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sm8250 Firmware, Qualcomm Sxr2130 Firmware.

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

Apply the vendor's patch.

## Is CVE-2020-3700 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8053 Firmware

- [CVE-2022-22071](https://insights.sbomify.com/CVE-2022-22071/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11153](https://insights.sbomify.com/CVE-2020-11153/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-3703](https://insights.sbomify.com/CVE-2020-3703/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)
- [CVE-2019-14080](https://insights.sbomify.com/CVE-2019-14080/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2020-3628](https://insights.sbomify.com/CVE-2020-3628/): Information disclosure in Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-3700 is a high-severity vulnerability in Qualcomm Apq8053 Firmware, published on 30 Jul 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-3700 in the wild and no public exploit code.

Affected product: Qualcomm Apq8053 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-3700/ (Markdown: https://insights.sbomify.com/CVE-2020-3700/index.md)
```

## Sources

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

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