# CVE-2021-1954: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking

> A buffer over-read in Qualcomm Snapdragon firmware allows attackers to cause denial of service or disclose sensitive information via crafted FILS indication frames.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jul 2021
- **Updated:** 3 Aug 2024
- **Also known as:** 2842475, A-184561797, ASB-A-184561797, GHSA-hhqw-7mxf-q7rx

## What is CVE-2021-1954?

CVE-2021-1954 is a high-severity memory corruption vulnerability in Qualcomm Apq8053 Firmware, published on 13 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Possible buffer over read due to improper validation of data pointer while parsing FILS indication IE in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking

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

## Which versions are affected by CVE-2021-1954?

It affects 150 products.


Products: Qualcomm Apq8053 Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar9380 Firmware, Qualcomm Csr8811 Firmware, Qualcomm Ipq4018 Firmware, Qualcomm Ipq4019 Firmware, Qualcomm Ipq4028 Firmware, Qualcomm Ipq4029 Firmware, Qualcomm Ipq5010 Firmware, Qualcomm Ipq5018 Firmware, Qualcomm Ipq5028 Firmware, Qualcomm Ipq6010 Firmware, Qualcomm Ipq6018 Firmware, Qualcomm Ipq6028 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Ipq8065 Firmware, Qualcomm Ipq8068 Firmware, Qualcomm Ipq8070 Firmware, Qualcomm Ipq8070a Firmware, Qualcomm Ipq8071 Firmware and 130 more.

## How do I fix CVE-2021-1954?

Apply the vendor's patch.

## Is CVE-2021-1954 being exploited?

There is no known exploitation of CVE-2021-1954 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-2021-1954 and fix it if it is affected.

What it is: CVE-2021-1954 is a high-severity memory corruption vulnerability in Qualcomm Apq8053 Firmware, published on 13 Jul 2021. 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-2021-1954 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-2021-1954/ (Markdown: https://insights.sbomify.com/CVE-2021-1954/index.md)
```

## Sources

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

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