# CVE-2018-11935: Other in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

> Improper input validation in Qualcomm Snapdragon firmware may return incorrect application IDs, potentially affecting system integrity or access control.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gxw6-6739-wjpf

## What is CVE-2018-11935?

CVE-2018-11935 is a medium-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 25 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper input validation might result in incorrect app id returned to the caller Instead of returning failure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in versions MDM9607, MDM9650, MDM9655, MSM8996AU, QCS605, SD 210/SD 212/SD 205, SD 410/12, SD 615/16/SD 415, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 8CX, SDA660, SDM630, SDM660, SXR1130.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-11935?

It affects 28 products.


Products: Qualcomm Mdm9607 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Mdm9655 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sd 12 Firmware, Qualcomm Sd 16 Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 410 Firmware, Qualcomm Sd 415 Firmware, Qualcomm Sd 615 Firmware, Qualcomm Sd 636 Firmware, Qualcomm Sd 670 Firmware, Qualcomm Sd 675 Firmware, Qualcomm Sd 710 Firmware, Qualcomm Sd 712 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 820a Firmware and 8 more.

## How do I fix CVE-2018-11935?

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

## Is CVE-2018-11935 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9607 Firmware

- [CVE-2019-10531](https://insights.sbomify.com/CVE-2019-10531/): Memory corruption in Snapdragon Auto, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2276](https://insights.sbomify.com/CVE-2019-2276/): Memory corruption in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)
- [CVE-2018-5915](https://insights.sbomify.com/CVE-2018-5915/): Denial of service in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2015-9126](https://insights.sbomify.com/CVE-2015-9126/): Memory corruption in Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2016-10479](https://insights.sbomify.com/CVE-2016-10479/): Memory corruption in Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-11935 and fix it if it is affected.

What it is: CVE-2018-11935 is a medium-severity vulnerability in Qualcomm Mdm9607 Firmware, published on 25 Feb 2019. 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-2018-11935 in the wild and no public exploit code.

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

## Sources

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

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