# CVE-2016-9917: Memory corruption in n/a

> A buffer overflow in BlueZ hcidump allows attackers to cause a denial of service by processing a corrupted dump file.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-9917, GHSA-2whh-5gr2-6f5w, ROOT-OS-DEBIAN-12-CVE-2016-9917, UBUNTU-CVE-2016-9917

## What is CVE-2016-9917?

CVE-2016-9917 is a high-severity memory corruption vulnerability in n/a, published on 8 Dec 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In BlueZ 5.42, a buffer overflow was observed in "read_n" function in "tools/hcidump.c" source file. This issue can be triggered by processing a corrupted dump file and will result in hcidump crash.

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

## Which versions are affected by CVE-2016-9917?

It affects 1 product.


Products: Bluez Bluez.

## How do I fix CVE-2016-9917?

Apply the vendor's patch.

## Is CVE-2016-9917 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-43400](https://insights.sbomify.com/CVE-2021-43400/): Use after free in n/a (critical 9.1)
- [CVE-2024-8805](https://insights.sbomify.com/CVE-2024-8805/): BlueZ HID over GATT Profile Improper Access Control Remote Code Execution Vulnerability (high 8.8)
- [CVE-2022-39176](https://insights.sbomify.com/CVE-2022-39176/): Information disclosure in n/a (high 8.8)
- [CVE-2022-39177](https://insights.sbomify.com/CVE-2022-39177/): Denial of service in n/a (high 8.8)
- [CVE-2022-0204](https://insights.sbomify.com/CVE-2022-0204/): Memory corruption in bluez (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9917 and fix it if it is affected.

What it is: CVE-2016-9917 is a high-severity memory corruption vulnerability in n/a, published on 8 Dec 2016. 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-2016-9917 in the wild and no public exploit code.

Affected product: n/a. 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-2016-9917/ (Markdown: https://insights.sbomify.com/CVE-2016-9917/index.md)
```

## Sources

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

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