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

> A buffer overflow in Qualcomm Snapdragon OEM crypto functions allows attackers to execute arbitrary code or escalate privileges via improper input validation.

- **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:** 28 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-825r-j36p-8hq9

## What is CVE-2018-5917?

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

### Official description

Possible buffer overflow in OEM crypto function due to improper input validation in Snapdragon Automobile, Snapdragon Mobile in versions MSM8996AU, SD 425, SD 430, SD 450, SD 625, SD 820, SD 820A, SD 835, SD 845, SD 850, SDA660, SDA845, SDX24, SXR1130.

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

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

It affects 14 products.


Products: Qualcomm Msm8996au Firmware, Qualcomm Sd 425 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 820a Firmware, Qualcomm Sd 835 Firmware, Qualcomm Sd 845 Firmware, Qualcomm Sd 850 Firmware, Qualcomm Sda660 Firmware, Qualcomm Sda845 Firmware, Qualcomm Sdx24 Firmware, Qualcomm Sxr1130 Firmware.

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

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

## Is CVE-2018-5917 being exploited?

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

## Other vulnerabilities in Qualcomm Msm8996au Firmware

- [CVE-2017-18318](https://insights.sbomify.com/CVE-2017-18318/): Security feature bypass in Snapdragon Automobile, Snapdragon Mobile (critical 9.8)
- [CVE-2024-45555](https://insights.sbomify.com/CVE-2024-45555/): Integer Overflow to Buffer Overflow in Automotive OS Platform (high 8.4)
- [CVE-2022-33282](https://insights.sbomify.com/CVE-2022-33282/): Integer overflow to buffer overflow in Automotive Multimedia (high 8.4)
- [CVE-2022-25680](https://insights.sbomify.com/CVE-2022-25680/): Memory corruption in Snapdragon Auto (high 8.4)
- [CVE-2024-53030](https://insights.sbomify.com/CVE-2024-53030/): Improper Input Validation in Automotive OS Platform (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-5917 is a high-severity memory corruption vulnerability in Qualcomm Msm8996au Firmware, published on 28 Nov 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-5917 in the wild and no public exploit code.

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

## Sources

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

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