# CVE-2020-3617: Information disclosure in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

> A buffer over-read in the Q6 testbus framework allows attackers to disclose sensitive information from memory in affected Qualcomm Snapdragon devices.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j5fp-59mp-fgm2

## What is CVE-2020-3617?

CVE-2020-3617 is a high-severity vulnerability in Qualcomm Kamorta Firmware, published on 9 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

u'Buffer over-read Issue in Q6 testbus framework due to diag packet length is not completely validated before accessing the field and leads to Information disclosure.' in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in Kamorta, Nicobar, QCS605, QCS610, Rennell, SC7180, SDA660, SDM630, SDM636, SDM660, SDM670, SDM710, SM6150, SM7150, SM8150, SXR1130

Weakness: CWE-20 (Improper Input Validation), CWE-125 (Out-of-bounds Read)

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

It affects 16 products.


Products: Qualcomm Kamorta Firmware, Qualcomm Nicobar Firmware, Qualcomm Qcs605 Firmware, Qualcomm Qcs610 Firmware, Qualcomm Rennell Firmware, Qualcomm Sc7180 Firmware, Qualcomm Sda660 Firmware, Qualcomm Sdm630 Firmware, Qualcomm Sdm636 Firmware, Qualcomm Sdm660 Firmware, Qualcomm Sdm670 Firmware, Qualcomm Sdm710 Firmware, Qualcomm Sm6150 Firmware, Qualcomm Sm7150 Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sxr1130 Firmware.

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

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

## Is CVE-2020-3617 being exploited?

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

## Other vulnerabilities in Qualcomm Kamorta Firmware

- [CVE-2019-14056](https://insights.sbomify.com/CVE-2019-14056/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2019-14089](https://insights.sbomify.com/CVE-2019-14089/): Security feature bypass in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2020-3636](https://insights.sbomify.com/CVE-2020-3636/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2019-14123](https://insights.sbomify.com/CVE-2019-14123/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2019-14124](https://insights.sbomify.com/CVE-2019-14124/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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