CVE-2018-1114: Uncontrolled Resource Consumption in Undertow

io.undertow:undertow-core Updated 02 Oct 2025

Summary

13/05/2022
Yes i
Moderate
6.5

CVE-2018-1114: Uncontrolled Resource Consumption in Undertow. Affects io.undertow:undertow-core across 2 version ranges.

< 1.4.25.Final >= 2.0.0.Alpha1, < 2.0.5.Final

Fixed in 1.4.25.Final or 2.0.5.Final, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2018-1114 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Undertow is a lightweight web server written in Java that is used for building high-performance web applications. It provides a flexible and extensible architecture for handling HTTP requests and responses. Undertow is widely used in various Java-based web frameworks and applications.

Vulnerability Detail

The vulnerability (CVE-2018-1114) in Undertow arises from the URLResource.getLastModified() function, which fails to properly close file descriptors. This can lead to a depletion of file descriptors and result in a file handler leak. An attacker could potentially exploit this vulnerability to exhaust system resources, leading to denial of service (DoS) conditions. The severity of this vulnerability is rated as MODERATE with a CVSS score of 6.5.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 1.4.25.Final 1.4.25.Final
  • >= 2.0.0.Alpha1, < 2.0.5.Final 2.0.5.Final

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

If updating to the fixed versions is not immediately feasible, a temporary workaround can be implemented by modifying the code to explicitly close file descriptors after they are no longer needed. Here is an example of how this can be done in Java:

try (FileInputStream fis = new FileInputStream(file)) {
    // Use the file input stream
} catch (IOException e) {
    // Handle the exception
}

By using the try-with-resources statement, the file input stream will be automatically closed after it is used, ensuring that file descriptors are properly released.

Conclusion

The vulnerability (CVE-2018-1114) in Undertow exposes a potential resource exhaustion issue due to improper handling of file descriptors. It is crucial to update to the fixed versions of Undertow (1.4.25.Final or 2.0.5.Final) to mitigate this vulnerability. If immediate update is not possible, implementing the provided workaround can help prevent resource exhaustion. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for io.undertow:undertow-core →

Share this vulnerability

FAQ

Undertow is a lightweight web server written in Java that is used for building high-performance web applications. It provides a flexible and extensible architecture for handling HTTP requests and responses.

The vulnerability in Undertow can lead to resource exhaustion, potentially resulting in denial of service (DoS) conditions. An attacker could exploit this vulnerability to exhaust system resources, causing disruption to the affected application or system.

The severity of this vulnerability is rated as MODERATE with a CVSS score of 6.5.

To fix this vulnerability, it is recommended to update the affected version of Undertow to at least version 1.4.25.Final for undertow-core 1.x.x or version 2.0.5.Final for undertow-core 2.x.x. These versions include the necessary fixes to properly close file descriptors and prevent resource exhaustion.

If updating to the fixed versions is not immediately feasible, a temporary workaround can be implemented by modifying the code to explicitly close file descriptors after they are no longer needed. Refer to the 'workaround' section for an example of how this can be done in Java.

Related vulnerabilities

Recent vulnerabilities recorded for io.undertow:undertow-core.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 1.4.25.Final 1.4.25.Final
  • >= 2.0.0.Alpha1, < 2.0.5.Final 2.0.5.Final

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback