# CVE-2018-11871: Memory corruption in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear

> A buffer overflow in the WLAN driver allows attackers to execute arbitrary code or escalate privileges on affected Qualcomm devices.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 29 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wr4r-8qpw-gr6r

## What is CVE-2018-11871?

CVE-2018-11871 is a high-severity memory corruption vulnerability in Qualcomm Ipq4019 Firmware, published on 29 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overwrite can happen in WLAN function while processing set pdev parameter command due to lack of input validation in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear in version IPQ4019, IPQ8064, IPQ8074, MDM9206, MDM9607, MDM9635M, MDM9640, MDM9650, MSM8996AU, QCA6174A, QCA6564, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA9377, QCA9378, QCA9379, QCA9531, QCA9558, QCA9563, QCA9880, QCA9886, QCA9980, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 450, SD 600, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SD 845, SD 850, SDA660, SDM630, SDM632, SDM636, SDM660, SDM710, SDX20, Snapdragon_High_Med_2016.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 49 products.


Products: Qualcomm Ipq4019 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Ipq8074 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9635m Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6564 Firmware, Qualcomm Qca6574 Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6584 Firmware, Qualcomm Qca6584au Firmware, Qualcomm Qca9377 Firmware, Qualcomm Qca9378 Firmware, Qualcomm Qca9379 Firmware, Qualcomm Qca9531 Firmware, Qualcomm Qca9558 Firmware and 29 more.

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

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

## Is CVE-2018-11871 being exploited?

There is no known exploitation of CVE-2018-11871 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-11871 and fix it if it is affected.

What it is: CVE-2018-11871 is a high-severity memory corruption vulnerability in Qualcomm Ipq4019 Firmware, published on 29 Oct 2018. 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-11871 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-11871/ (Markdown: https://insights.sbomify.com/CVE-2018-11871/index.md)
```

## Sources

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

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