# CVE-2017-18070: Integer overflow in Android for MSM, Firefox OS for MSM, QRD Android

> An integer overflow in the Qualcomm Android kernel allows heap overwrites, potentially enabling code execution or privilege escalation.

- **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:** 12 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-3w73-8wv6-hfqr

## What is CVE-2017-18070?

CVE-2017-18070 is a high-severity vulnerability in Google Android, published on 12 Jun 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In wma_ndp_end_response_event_handler(), the variable len_end_rsp is a uint32 which can be overflowed if the value of variable "event->num_ndp_end_rsp_per_ndi_list" is very large which can then lead to a heap overwrite of the heap object end_rsp in all Android releases from CAF (Android for MSM, Firefox OS for MSM, QRD Android) using the Linux Kernel.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Google Android.

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

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

## Is CVE-2017-18070 being exploited?

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

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18070 is a high-severity vulnerability in Google Android, published on 12 Jun 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-18070 in the wild and no public exploit code.

Affected product: Google Android. 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-18070/ (Markdown: https://insights.sbomify.com/CVE-2017-18070/index.md)
```

## Sources

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

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