# CVE-2018-11942: Information disclosure in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking

> Uninitialized kernel memory exposure to firmware allows attackers to read sensitive data from Snapdragon devices.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 14 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m7h5-w424-74x3

## What is CVE-2018-11942?

CVE-2018-11942 is a medium-severity vulnerability in Qualcomm Ipq4019 Firmware, published on 14 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Failure to initialize the reserved memory which is sent to the firmware might lead to exposure of 1 byte of uninitialized kernel SKB memory to FW in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in IPQ4019, IPQ8064, IPQ8074, MDM9150, MDM9206, MDM9607, MDM9640, MDM9650, MSM8996AU, QCS405, QCS605, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDA660, SDM630, SDM660, SDX20, SDX24

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

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

It affects 33 products.


Products: Qualcomm Ipq4019 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Ipq8074 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 427 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 435 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 636 Firmware, Qualcomm Sd 670 Firmware, Qualcomm Sd 675 Firmware and 13 more.

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

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

## Is CVE-2018-11942 being exploited?

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

## Other vulnerabilities in Qualcomm Ipq4019 Firmware

- [CVE-2020-11172](https://insights.sbomify.com/CVE-2020-11172/): Memory corruption in Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-11117](https://insights.sbomify.com/CVE-2020-11117/): Command injection in Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2014-10045](https://insights.sbomify.com/CVE-2014-10045/): Memory corruption in Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2014-9988](https://insights.sbomify.com/CVE-2014-9988/): Memory corruption in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2014-9998](https://insights.sbomify.com/CVE-2014-9998/): In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear IPQ40 (critical 9.8)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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