dbcve.org
UndertowApplication · Redhat

CVE-2024-1459

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
A path traversal vulnerability was found in Undertow. This issue may allow a remote attacker to append a specially-crafted sequence to an HTTP request for an application deployed to JBoss EAP, which may permit access to privileged or restricted files and directories.

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 · moderate confidence

Path traversal vulnerability in Undertow allows remote attackers to append specially-crafted sequences to HTTP requests for JBoss EAP deployed applications, potentially accessing restricted files and directories outside the web root.

MitigationUpdate Undertow to a patched version via JBoss EAP security update, and implement strict input validation on file path parameters to reject traversal sequences.

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:all versions

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 if Undertow is in use
    Search for undertow-core.jar or undertow-servlet.jar files in your JBoss EAP installation directory (typically under $JBOSS_HOME/modules/system/layers/base/io/undertow/). You can run: find $JBOSS_HOME -name 'undertow*.jar' 2>/dev/null
    Affected if Undertow JAR files are found in the JBoss EAP installation
  2. Check Undertow version
    Examine the manifest file inside the Undertow JAR or check the version in the module.xml descriptor. Run: unzip -p $JBOSS_HOME/modules/system/layers/base/io/undertow/main/undertow-core-*.jar META-INF/MANIFEST.MF | grep Implementation-Version
    Affected if All versions are affected according to the CVE, but confirming the exact version helps with patching decisions
  3. Verify web applications handle file paths
    Inspect deployed web applications (WAR files) for code that processes file paths from HTTP request parameters (e.g., getParameter, request.getQueryString). Search for patterns like new File(), Paths.get(), or FileInputStream with request-derived paths
    Affected if Applications process file paths derived from user input without validation
  4. Check web root configuration
    Review the jboss-web.xml descriptor in deployed WAR files (under WEB-INF/) and verify the document-root attribute. Also check undertow's handlers configuration in standalone.xml for any custom file handlers
    Affected if The document root allows access outside the intended web root or custom file handlers accept traversal sequences
  5. Test for path traversal vulnerability
    Send a test HTTP request with traversal sequences to your application's endpoints (e.g., /..%2F..%2F..%2Fetc%2Fpasswd or /..\..\..\windows\system32\drivers\etc\hosts). Monitor if restricted files outside the web root are accessible
    Affected if The application returns content from files outside the configured web root directory

If Undertow is present and your deployed applications accept file path parameters from HTTP requests without strict validation, your environment is likely affected by this path traversal vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Undertow to a patched version via JBoss EAP security update, and implement strict input validation on file path parameters to reject traversal sequences.

Fix this in Undertow Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1459 — 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-2024-1459 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