# CVE-2018-5871: Weak cryptography in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear

> Flawed random number generation in Qualcomm Snapdragon firmware allows attackers to bypass MAC address randomization privacy protections.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6gwf-ww2j-gfrq

## What is CVE-2018-5871?

CVE-2018-5871 is a medium-severity vulnerability in Qualcomm Mdm9206 Firmware, published on 20 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Snapdragon (Automobile, Mobile, Wear) in version MDM9206, MDM9607, MDM9640, MDM9650, MSM8996AU, QCA6574AU, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 820A, SD 835, SD 845, SD 850, SDA660, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, SDM710, Snapdragon_High_Med_2016, MAC address randomization performed during probe requests (for privacy reasons) is not done properly due to a flawed RNG which produces repeating output much earlier than expected.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

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

It affects 31 products.


Products: Qualcomm Mdm9206 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca6574au Firmware, Qualcomm Sd205 Firmware, Qualcomm Sd210 Firmware, Qualcomm Sd212 Firmware, Qualcomm Sd415 Firmware, Qualcomm Sd425 Firmware, Qualcomm Sd427 Firmware, Qualcomm Sd430 Firmware, Qualcomm Sd435 Firmware, Qualcomm Sd450 Firmware, Qualcomm Sd615 Firmware, Qualcomm Sd616 Firmware, Qualcomm Sd650 Firmware, Qualcomm Sd652 Firmware, Qualcomm Sd820a Firmware and 11 more.

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

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

## Is CVE-2018-5871 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9206 Firmware

- [CVE-2016-10394](https://insights.sbomify.com/CVE-2016-10394/): Improper Authentication in Core (critical 9.8)
- [CVE-2019-10522](https://insights.sbomify.com/CVE-2019-10522/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10528](https://insights.sbomify.com/CVE-2019-10528/): Use after free in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10533](https://insights.sbomify.com/CVE-2019-10533/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10534](https://insights.sbomify.com/CVE-2019-10534/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-5871 is a medium-severity vulnerability in Qualcomm Mdm9206 Firmware, published on 20 Sep 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-5871 in the wild and no public exploit code.

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

## Sources

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

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