# CVE-2019-11516: Memory corruption in n/a

> Heap-based buffer overflow in Cypress Bluetooth stack allows remote code execution via crafted Extended Inquiry Responses.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 5 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6624-pmgq-j9j4

## What is CVE-2019-11516?

CVE-2019-11516 is a high-severity memory corruption vulnerability in Google Android, published on 5 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the Bluetooth component of the Cypress (formerly owned by Broadcom) Wireless IoT codebase. Extended Inquiry Responses (EIRs) are improperly handled, which causes a heap-based buffer overflow during device inquiry. This overflow can be used to overwrite existing functions with arbitrary code. The Reserved for Future Use (RFU) bits are not discarded by eir_handleRx(), and are included in an EIR's length. Therefore, one can exceed the expected 240 bytes, which leads to a heap-based buffer overflow in eir_getReceivedEIR() called by bthci_event_SendInquiryResultEvent(). In order to exploit this bug, an attacker must repeatedly connect to the victim's device in a short amount of time from different source addresses. This will cause the victim's Bluetooth stack to resolve the device names and therefore allocate buffers with attacker-controlled data. Due to the heap corruption, the name will be eventually written to an attacker-controlled location, leading to a write-what-where condition.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-11516?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2019-11516?

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

## Is CVE-2019-11516 being exploited?

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

What it is: CVE-2019-11516 is a high-severity memory corruption vulnerability in Google Android, published on 5 Feb 2020. 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-2019-11516 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-2019-11516/ (Markdown: https://insights.sbomify.com/CVE-2019-11516/index.md)
```

## Sources

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

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