# CVE-2021-1957: Security feature bypass in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

> Attackers can bypass ACL link encryption and maintain unauthorized connections during reconnection in Qualcomm Snapdragon devices.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Sep 2021
- **Updated:** 3 Aug 2024
- **Also known as:** 2427750, A-181677124, GHSA-8pqm-hrrp-373j, PUB-A-181677124

## What is CVE-2021-1957?

CVE-2021-1957 is a medium-severity vulnerability in Qualcomm Apq8017 Firmware, published on 9 Sep 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Access Control when ACL link encryption is failed and ACL link is not disconnected during reconnection with paired device in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

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

It affects 46 products.


Products: Qualcomm Apq8017 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6421 Firmware, Qualcomm Qca6426 Firmware, Qualcomm Qca6431 Firmware, Qualcomm Qca6436 Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6696 Firmware, Qualcomm Qcm6125 Firmware, Qualcomm Qcs610 Firmware, Qualcomm Qcs6125 Firmware, Qualcomm Qrb5165 Firmware, Qualcomm Qualcomm215 Firmware, Qualcomm Sa6145p Firmware, Qualcomm Sa6150p Firmware, Qualcomm Sa6155p Firmware, Qualcomm Sa8145p Firmware, Qualcomm Sa8150p Firmware and 26 more.

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

Apply the vendor's patch.

## Is CVE-2021-1957 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8017 Firmware

- [CVE-2025-21483](https://insights.sbomify.com/CVE-2025-21483/): Improper Restriction of Operations within the Bounds of a Memory Buffer in Data Network Stack & Connectivity (critical 9.8)
- [CVE-2021-1933](https://insights.sbomify.com/CVE-2021-1933/): Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables (critical 9.8)
- [CVE-2021-1946](https://insights.sbomify.com/CVE-2021-1946/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-11176](https://insights.sbomify.com/CVE-2020-11176/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-11291](https://insights.sbomify.com/CVE-2020-11291/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-1957 and fix it if it is affected.

What it is: CVE-2021-1957 is a medium-severity vulnerability in Qualcomm Apq8017 Firmware, published on 9 Sep 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-1957 in the wild and no public exploit code.

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

## Sources

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

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