# CVE-2017-18315: Memory corruption in Snapdragon Mobile

> A buffer over-read in the Snapdragon Mobile ASN.1 parser allows attackers to cause denial of service or disclose sensitive memory information.

- **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-29p8-v995-43v6

## What is CVE-2017-18315?

CVE-2017-18315 is a high-severity memory corruption vulnerability in Qualcomm Sd 600 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

Buffer over-read vulnerabilities in an older version of ASN.1 parser in Snapdragon Mobile in versions SD 600.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2017-18315?

It affects 1 product.


Products: Qualcomm Sd 600 Firmware.

## How do I fix CVE-2017-18315?

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

## Is CVE-2017-18315 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18315 and fix it if it is affected.

What it is: CVE-2017-18315 is a high-severity memory corruption vulnerability in Qualcomm Sd 600 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-2017-18315 in the wild and no public exploit code.

Affected product: Qualcomm Sd 600 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-2017-18315/ (Markdown: https://insights.sbomify.com/CVE-2017-18315/index.md)
```

## Sources

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

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