# CVE-2017-10872: Denial of service in H2O

> Remote attackers can cause a denial of service in the H2O web server via unspecified vectors, requiring an upgrade to mitigate.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-10872, GHSA-gq8c-8c44-g5xc

## What is CVE-2017-10872?

CVE-2017-10872 is a medium-severity denial of service vulnerability in Kazuho Oku H2O, published on 22 Dec 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

H2O version 2.2.3 and earlier allows remote attackers to cause a denial of service in the server via unspecified vectors.

Weakness: CWE-118 (Incorrect Access of Indexable Resource)

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

It affects 1 product.


Products: Dena H2o.

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

Upgrade to a fixed version.

## Is CVE-2017-10872 being exploited?

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

## Other vulnerabilities in Kazuho Oku H2O

- [CVE-2018-0608](https://insights.sbomify.com/CVE-2018-0608/): Memory corruption in H2O (critical 9.8)
- [CVE-2016-7835](https://insights.sbomify.com/CVE-2016-7835/): Use after free in H2O (critical 9.1)
- [CVE-2023-30847](https://insights.sbomify.com/CVE-2023-30847/): H2O vulnerable to read from uninitialized pointer in the reverse proxy handler (high 8.2)
- [CVE-2017-10868](https://insights.sbomify.com/CVE-2017-10868/): Denial of service in H2O (high 7.5)
- [CVE-2017-10869](https://insights.sbomify.com/CVE-2017-10869/): Memory corruption in H2O (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10872 is a medium-severity denial of service vulnerability in Kazuho Oku H2O, published on 22 Dec 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10872 in the wild and no public exploit code.

Affected product: Kazuho Oku H2O. 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-10872/ (Markdown: https://insights.sbomify.com/CVE-2017-10872/index.md)
```

## Sources

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

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