dbcve.org
UndertowApplication · Redhat

CVE-2018-1067

MEDIUM · 6.1 CVSS v3.1 Published 2018-05-21
Fix available
A fix is available. Upgrade to 1.4.25 / 2.0.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Undertow before versions 7.1.2.CR1, 7.1.2.GA it was found that the fix for CVE-2016-4993 was incomplete and Undertow web server is vulnerable to the injection of arbitrary HTTP headers, and also response splitting, due to insufficient sanitization and validation of user input before the input is used as part of an HTTP header value.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Undertow web server before versions 7.1.2.CR1 and 7.1.2.GA contains an incomplete fix for CVE-2016-4993, allowing injection of arbitrary HTTP headers and HTTP response splitting due to insufficient sanitization and validation of user input before being used in HTTP header values.

MitigationUpgrade Undertow to version 7.1.2.CR1 or later. Additionally, implement robust input validation and sanitization for all user-supplied data before using it in HTTP headers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
UndertowApplication
Affected:< 1.4.25>= 2.0.0, < 2.0.5
Jboss Enterprise Application PlatformApplication
Affected:= 7.1
Virtualization HostApplication
Affected:= 4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Undertow installation and version
    Locate the undertow-core jar file in your application dependencies or JBoss installation. Run: find . -name 'undertow-core*.jar' 2>/dev/null or check your Maven/Gradle dependencies for undertow version. Also check the JBoss EAP installation bin/standalone.sh --version if applicable.
    Affected if The installed version is 1.4.x below 1.4.25, or 2.0.x below 2.0.5, or 7.1.x (JBoss EAP 7.1)
  2. Verify Redhat Virtualization Host version
    If running Redhat Virtualization Host 4.0, check the bundled undertow version by examining /usr/share/undertow/lib/ or the RPM package: rpm -qa | grep undertow
    Affected if Virtualization Host 4.0 ships with vulnerable undertow version bundled
  3. Audit application code for header value handling
    Search your application source code for patterns where user-supplied data (request parameters, headers, path segments) flows into HTTP response headers. Look for: response.setHeader(), response.addHeader(), or similar APIs receiving unsanitized input.
    Affected if Application passes any user input into HTTP headers without validation or sanitization
  4. Review Undertow handler configuration
    Examine your Undertow or JBoss configuration files (undertow.conf.xml, standalone.xml, or web.xml) for custom handlers that process and set HTTP headers based on user input.
    Affected if Custom handlers or filters are configured that inject user data into response headers

You are affected if your Undertow version is 1.4.x < 1.4.25, 2.0.x < 2.0.5, or JBoss EAP 7.1/Virtualization Host 4.0 AND your application uses user-supplied input in HTTP response headers without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.4.25 / 2.0.5 or later
Fixed in 1.4.252.0.5
Interim mitigation

Upgrade Undertow to version 7.1.2.CR1 or later. Additionally, implement robust input validation and sanitization for all user-supplied data before using it in HTTP headers.

Fix this in Undertow Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1067 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data