# CVE-2018-1114: Uncontrolled Resource Consumption in Undertow

> Attackers can exhaust file descriptors in Undertow by triggering URLResource.getLastModified(), causing a denial of service.

- **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:** 11 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-1114, GHSA-gjjx-gqm4-wcgm, UBUNTU-CVE-2018-1114

## What is CVE-2018-1114?

CVE-2018-1114 is a medium-severity denial of service vulnerability in Redhat Virtualization, published on 11 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

It was found that URLResource.getLastModified() in Undertow closes the file descriptors only when they are finalized which can cause file descriptors to exhaust. This leads to a file handler leak.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2018-1114?

4 open source packages ship an affected version, including io.undertow:undertow-core. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.undertow:undertow-core` | Maven | All versions | 1.4.25.Final |
| `io.undertow:undertow-core` | Maven | All versions | 1.4.25.Final |
| `io.undertow:undertow-core` | Maven | From 2.0.0.Alpha1 | 2.0.5.Final |
| `io.undertow:undertow-core` | Maven | From 2.0.0.Alpha1 | 2.0.5.Final |

Products: Redhat Undertow, Redhat Virtualization, Redhat Virtualization Host.

## How do I fix CVE-2018-1114?

Upgrade io.undertow:undertow-core to a fixed version for your release line: 1.4.25.Final or 2.0.5.Final.

## Is CVE-2018-1114 being exploited?

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

## Other vulnerabilities in Redhat Virtualization

- [CVE-2020-1745](https://insights.sbomify.com/CVE-2020-1745/): Improper Authorization in Undertoe (high 8.6)
- [CVE-2017-7559](https://insights.sbomify.com/CVE-2017-7559/): Undertow vulnerable to Request Smuggling (medium 6.1)
- [CVE-2024-1459](https://insights.sbomify.com/CVE-2024-1459/): Undertow: directory traversal vulnerability (medium 5.3)
- [CVE-2014-7816](https://insights.sbomify.com/CVE-2014-7816/): Improper Limitation of a Pathname to a Restricted Directory in JBoss Undertow (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1114 and fix it if it is affected.

What it is: CVE-2018-1114 is a medium-severity denial of service vulnerability in Redhat Virtualization, published on 11 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1114 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.undertow:undertow-core (Maven): affected all versions; fixed in 1.4.25.Final
- io.undertow:undertow-core (Maven): affected all versions; fixed in 1.4.25.Final
- io.undertow:undertow-core (Maven): affected from 2.0.0.Alpha1; fixed in 2.0.5.Final
- io.undertow:undertow-core (Maven): affected from 2.0.0.Alpha1; fixed in 2.0.5.Final

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-2018-1114/ (Markdown: https://insights.sbomify.com/CVE-2018-1114/index.md)
```

## Sources

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

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