# CVE-2015-8373: Denial of service in n/a

> Remote attackers can crash the Kea DHCP server via malformed packets when specific debugging settings are enabled.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/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:** No
- **Published:** 22 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mc48-v6m5-6qrr

## What is CVE-2015-8373?

CVE-2015-8373 is a medium-severity denial of service vulnerability in n/a, published on 22 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The kea-dhcp4 and kea-dhcp6 servers 0.9.2 and 1.0.0-beta in ISC Kea, when certain debugging settings are used, allow remote attackers to cause a denial of service (daemon crash) via a malformed packet.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2015-8373?

It affects 1 product.


Products: Isc Kea.

## How do I fix CVE-2015-8373?

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

## Is CVE-2015-8373 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-6472](https://insights.sbomify.com/CVE-2019-6472/): A packet containing a malformed DUID can cause the kea-dhcp6 server to terminate (medium 6.5)
- [CVE-2018-5739](https://insights.sbomify.com/CVE-2018-5739/): Failure to release memory may exhaust system resources (medium 6.5)
- [CVE-2019-6474](https://insights.sbomify.com/CVE-2019-6474/): A packet containing a malformed DUID can cause the kea-dhcp6 server to terminate (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8373 and fix it if it is affected.

What it is: CVE-2015-8373 is a medium-severity denial of service vulnerability in n/a, published on 22 Dec 2015. 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-2015-8373 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-2015-8373/ (Markdown: https://insights.sbomify.com/CVE-2015-8373/index.md)
```

## Sources

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

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