# CVE-2020-3611: Security feature bypass in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking

> Improper access control in Qualcomm Snapdragon firmware allows bypassing security restrictions during segment loading.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 8 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-v8qg-gvfx-g8vq

## What is CVE-2020-3611?

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

### Official description

u'XBL SEC clears only ZI region when loading Qualcomm-signed segments can lead to improper access issue' in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in APQ8098, Kamorta, MSM8998, QCS404, QCS605, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SXR1130

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

It affects 15 products.


Products: Qualcomm Apq8098 Firmware, Qualcomm Kamorta Firmware, Qualcomm Msm8998 Firmware, Qualcomm Qcs404 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sda660 Firmware, Qualcomm Sda845 Firmware, Qualcomm Sdm630 Firmware, Qualcomm Sdm636 Firmware, Qualcomm Sdm660 Firmware, Qualcomm Sdm670 Firmware, Qualcomm Sdm710 Firmware, Qualcomm Sdm845 Firmware, Qualcomm Sdm850 Firmware, Qualcomm Sxr1130 Firmware.

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

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

## Is CVE-2020-3611 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8098 Firmware

- [CVE-2020-3667](https://insights.sbomify.com/CVE-2020-3667/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-3669](https://insights.sbomify.com/CVE-2020-3669/): 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 (critical 9.8)
- [CVE-2019-14112](https://insights.sbomify.com/CVE-2019-14112/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2019-14086](https://insights.sbomify.com/CVE-2019-14086/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-11206](https://insights.sbomify.com/CVE-2020-11206/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (high 7.8)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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