It was discovered that Undertow before 1.4.17, 1.3.31 and 2.0.0 processes http request headers with unusual whitespaces which can cause poss
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 78.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: undertow (Debian:14) 2.0.23-1; io.undertow:undertow-core (Maven) 1.4.17, 2.0.0.Beta1, 1.3.31; eap7-activemq-artemis (Red Hat:jboss_enterprise_application_platform:7::el6) 0:1.5.5.008-1.redhat_1.1.ep7.el6, 0:1.1.0-19.SP24_redhat_1.1.ep7.el6.
- Severity is disputed: the assigning authority (CNA) scores it 2.6, NVD 7.5.
Low priority for now. Upgrade to undertow (Debian:14) 2.0.23-1; io.undertow:undertow-core (Maven) 1.4.17, 2.0.0.Beta1, 1.3.31; eap7-activemq-artemis (Red Hat:jboss_enterprise_application_platform:7::el6) 0:1.5.5.008-1.redhat_1.1.ep7.el6, 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
It was discovered that Undertow before 1.4.17, 1.3.31 and 2.0.0 processes http request headers with unusual whitespaces which can cause possible http request smuggling.
- Published
- Jul 27, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- CWE-444
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
CNA vs NVD score
- NVD
- 7.5
- CNA · redhat
- 2.6
- 4.9 point gap
CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redhat | undertow | cpe:2.3:a:redhat:undertow |
| redhat | jboss enterprise application platform | cpe:2.3:a:redhat:jboss_enterprise_application_platform |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat jboss enterprise application platform7.0.0
- redhat jboss enterprise application platform7.1.0
- redhat undertow1.0.0 and later · before 1.3.31
- redhat undertow1.4.0 and later · before 1.4.17
- redhat undertow2.0.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Red Hat undertow
- 1.4.17, 1.3.31, 2.0.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | undertow | before 2.0.23-1 | 2.0.23-1 |
| Maven | io.undertow:undertow-core | from 1.4.0 · before 1.4.17 | 1.4.17 |
| Maven | io.undertow:undertow-core | from 2.0.0.Alpha1 · before 2.0.0.Beta1 | 2.0.0.Beta1 |
| Maven | io.undertow:undertow-core | before 1.3.31 | 1.3.31 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis | before 0:1.5.5.008-1.redhat_1.1.ep7.el6 | 0:1.5.5.008-1.redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis | before 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 | 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-cli | before 0:1.5.5.008-1.redhat_1.1.ep7.el6 | 0:1.5.5.008-1.redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-cli | before 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 | 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-commons | before 0:1.5.5.008-1.redhat_1.1.ep7.el6 | 0:1.5.5.008-1.redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-commons | before 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 | 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-core-client | before 0:1.5.5.008-1.redhat_1.1.ep7.el6 | 0:1.5.5.008-1.redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-core-client | before 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 | 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-dto | before 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 | 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-dto | before 0:1.5.5.008-1.redhat_1.1.ep7.el6 | 0:1.5.5.008-1.redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-hornetq-protocol | before 0:1.5.5.008-1.redhat_1.1.ep7.el6 | 0:1.5.5.008-1.redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-hornetq-protocol | before 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 | 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-hqclient-protocol | before 0:1.5.5.008-1.redhat_1.1.ep7.el6 | 0:1.5.5.008-1.redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-hqclient-protocol | before 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 | 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-jdbc-store | before 0:1.5.5.008-1.redhat_1.1.ep7.el6 | 0:1.5.5.008-1.redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-jms-client | before 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 | 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-jms-client | before 0:1.5.5.008-1.redhat_1.1.ep7.el6 | 0:1.5.5.008-1.redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-jms-server | before 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 | 0:1.1.0-19.SP24_redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-jms-server | before 0:1.5.5.008-1.redhat_1.1.ep7.el6 | 0:1.5.5.008-1.redhat_1.1.ep7.el6 |
| Red Hat:jboss_enterprise_application_platform:7::el6 | eap7-activemq-artemis-journal | before 0:1.5.5.008-1.redhat_1.1.ep7.el6 | 0:1.5.5.008-1.redhat_1.1.ep7.el6 |
+96
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-1745A file inclusion vulnerability was found in the AJP connector enabled with a default AJP configuration port of 8009 in Undertow version 2.0.40Plan
- CVE-2019-10212A flaw was found in, all under 2.0.20, in the Undertow DEBUG log for io.undertow.request.security.40Plan
- CVE-2019-3888A vulnerability was found in Undertow web server before 2.0.21.40Plan
- CVE-2020-1757A flaw was found in all undertow-2.x.x SP1 versions prior to undertow-2.0.30.SP1, all undertow-1.x.x and undertow-2.x.x versions prior to un32Monitor
- CVE-2023-3223Undertow: outofmemoryerror due to @multipartconfig handling31Monitor
- CVE-2019-14888A vulnerability was found in the Undertow HTTP server in versions before 2.0.28.SP1 when listening on HTTPS.31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:undertow | 2.0.23-1 · Debian:14 | Package registry (OSV) |
| Maven:io.undertow:undertow-core | 1.3.31 | Package registry (OSV) |
| Maven:io.undertow:undertow-core | 1.4.17 | Package registry (OSV) |
| Maven:io.undertow:undertow-core | 2.0.0.Beta1 | Package registry (OSV) |
| red hat:eap7-activemq-artemis | 0:1.5.5.008-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6 | Package registry (OSV) |
| red hat:eap7-activemq-artemis-cli | 0:1.5.5.008-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6 | Package registry (OSV) |
| red hat:eap7-activemq-artemis-commons | 0:1.5.5.008-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6 | Package registry (OSV) |
| red hat:eap7-activemq-artemis-core-client | 0:1.5.5.008-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6 | Package registry (OSV) |
| red hat:eap7-activemq-artemis-dto | 0:1.5.5.008-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6 | Package registry (OSV) |
| red hat:eap7-activemq-artemis-hornetq-protocol | 0:1.5.5.008-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6 | Package registry (OSV) |
| red hat:eap7-activemq-artemis-hqclient-protocol | 0:1.5.5.008-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6 | Package registry (OSV) |
| red hat:eap7-activemq-artemis-jdbc-store | 0:1.5.5.008-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6 | Package registry (OSV) |
| red hat:eap7-activemq-artemis-jms-client | 0:1.5.5.008-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6 | Package registry (OSV) |
| red hat:eap7-activemq-artemis-jms-server | 0:1.5.5.008-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6 | Package registry (OSV) |
| red hat:eap7-activemq-artemis-journal | 0:1.5.5.008-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6 | Package registry (OSV) |
| red hat:eap7-activemq-artemis-native | 0:1.5.5.008-1.redhat_1.1.ep7.el6 · Red Hat:jboss_enterprise_application_platform:7::el6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-444 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- access.redhat.com/errata/RHSA-2017:3455
- access.redhat.com/errata/RHSA-2017:3456
- access.redhat.com/errata/RHSA-2017:3458
- access.redhat.com/errata/RHSA-2018:0002
- access.redhat.com/errata/RHSA-2018:0003
- access.redhat.com/errata/RHSA-2018:0004
- access.redhat.com/errata/RHSA-2018:0005
- access.redhat.com/errata/RHSA-2018:1322
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-12165
Vendor advisories and official records. Exploit/PoC links are deliberately left out.