# CVE-2021-30314: Information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> A lack of validation allows third-party applications to access services, leading to information disclosure in various Qualcomm Snapdragon platforms.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-7v89-wqr4-9x78

## What is CVE-2021-30314?

CVE-2021-30314 is a medium-severity vulnerability in Qualcomm Qca6390 Firmware, published on 13 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Lack of validation for third party application accessing the service can lead to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 74 products.


Products: Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6426 Firmware, Qualcomm Qca6436 Firmware, Qualcomm Qca6574 Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6595au Firmware, Qualcomm Qca6696 Firmware, Qualcomm Qcm2290 Firmware, Qualcomm Qcm4290 Firmware, Qualcomm Qcm6490 Firmware, Qualcomm Qcs2290 Firmware, Qualcomm Qcs4290 Firmware, Qualcomm Qcs603 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Qcs610 Firmware, Qualcomm Qcs6490 Firmware, Qualcomm Qualcomm215 Firmware, Qualcomm Sa6145p Firmware and 54 more.

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

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

## Is CVE-2021-30314 being exploited?

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

## Other vulnerabilities in Qualcomm Qca6390 Firmware

- [CVE-2021-30336](https://insights.sbomify.com/CVE-2021-30336/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Wearables (high 8.4)
- [CVE-2020-11156](https://insights.sbomify.com/CVE-2020-11156/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (high 8.1)
- [CVE-2023-21667](https://insights.sbomify.com/CVE-2023-21667/): Buffer Over-read in Bluetooth HOST (medium 6.5)
- [CVE-2023-21647](https://insights.sbomify.com/CVE-2023-21647/): Improper Input Validation in Bluetooth HOST (medium 6.5)
- [CVE-2019-10618](https://insights.sbomify.com/CVE-2019-10618/): Null dereference in Snapdragon Connectivity (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-30314 is a medium-severity vulnerability in Qualcomm Qca6390 Firmware, published on 13 Jan 2022. 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-30314 in the wild and no public exploit code.

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

## Sources

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

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