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

> Integer overflow in Qualcomm Android power debug handler allows buffer overflow, potentially enabling code execution or privilege escalation.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-h53p-95jp-7gv4

## What is CVE-2017-14883?

CVE-2017-14883 is a critical vulnerability in Google Android, published on 30 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the function wma_unified_power_debug_stats_event_handler() in Android for MSM, Firefox OS for MSM, and QRD Android before 2017-10-18, if the value param_buf->num_debug_register received from the FW command buffer is close to max of uint32, then the computation performed using this variable to calculate stats_registers_len may overflow to a smaller value leading to less than required memory allocated for power_stats_results and potentially a buffer overflow while copying the FW buffer to local buffer.

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

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

It affects 1 product.


Products: Google Android.

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

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

## Is CVE-2017-14883 being exploited?

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

What it is: CVE-2017-14883 is a critical vulnerability in Google Android, published on 30 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14883 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-14883/ (Markdown: https://insights.sbomify.com/CVE-2017-14883/index.md)
```

## Sources

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

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