# CVE-2020-3628: Information disclosure in Snapdragon Consumer IOT, Snapdragon Mobile

> An improper access control in the logging application allows attackers to read sensitive data from Snapdragon devices.

- **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:** 22 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g778-c6cg-9fmw

## What is CVE-2020-3628?

CVE-2020-3628 is a critical vulnerability in Qualcomm Apq8053 Firmware, published on 22 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper access due to socket opened by the logging application without specifying localhost address in Snapdragon Consumer IOT, Snapdragon Mobile in APQ8053, Rennell, SDX20

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

It affects 3 products.


Products: Qualcomm Apq8053 Firmware, Qualcomm Rennell Firmware, Qualcomm Sdx20 Firmware.

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

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

## Is CVE-2020-3628 being exploited?

There is no known exploitation of CVE-2020-3628 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-2019-14131](https://insights.sbomify.com/CVE-2019-14131/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-3628 is a critical vulnerability in Qualcomm Apq8053 Firmware, published on 22 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-3628 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-3628/ (Markdown: https://insights.sbomify.com/CVE-2020-3628/index.md)
```

## Sources

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

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