# CVE-2018-1067: Improper Neutralization of CRLF Sequences in HTTP Headers in Undertow

> Attackers can inject arbitrary HTTP headers or split responses in Undertow due to insufficient input sanitization, potentially bypassing security controls.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-1067, GHSA-47mp-rq2x-wjf2, UBUNTU-CVE-2018-1067

## What is CVE-2018-1067?

CVE-2018-1067 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 21 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-113 (Improper Neutralization of CRLF Sequences in HTTP Headers)

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

2 open source packages ship an affected version, including org.jboss.eap:wildfly-undertow. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jboss.eap:wildfly-undertow` | Maven | All versions | 7.1.2.GA |
| `org.jboss.eap:wildfly-undertow` | Maven | All versions | 7.1.2.GA |

Products: Redhat Jboss Enterprise Application Platform, Redhat Undertow, Redhat Virtualization Host.

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

Upgrade org.jboss.eap:wildfly-undertow to 7.1.2.GA or later.

## Is CVE-2018-1067 being exploited?

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

## Other vulnerabilities in Redhat Jboss Enterprise Application Platform

- [CVE-2017-12149](https://insights.sbomify.com/CVE-2017-12149/): Red Hat JBoss Application Server Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2010-1428](https://insights.sbomify.com/CVE-2010-1428/): Red Hat JBoss Information Disclosure (medium 5.9, exploited in the wild)
- [CVE-2010-0738](https://insights.sbomify.com/CVE-2010-0738/): Red Hat JBoss Authentication Bypass (low 3.7, exploited in the wild)
- [CVE-2016-3690](https://insights.sbomify.com/CVE-2016-3690/): Deserialization in n/a (critical 9.8)
- [CVE-2017-7504](https://insights.sbomify.com/CVE-2017-7504/): Deserialization in JBoss (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1067 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 21 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1067 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jboss.eap:wildfly-undertow (Maven): affected all versions; fixed in 7.1.2.GA
- org.jboss.eap:wildfly-undertow (Maven): affected all versions; fixed in 7.1.2.GA

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

## Sources

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

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