UndertowApplication · Redhat
CVE-2014-7816
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 · uneditedDirectory traversal vulnerability in JBoss Undertow 1.0.x before 1.0.17, 1.1.x before 1.1.0.CR5, and 1.2.x before 1.2.0.Beta3, when running on Windows, allows remote attackers to read arbitrary files via a .. (dot dot) in a resource URI.
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 confidenceDirectory traversal vulnerability in JBoss Undertow allows remote attackers to read arbitrary files on Windows systems by using '..' (dot-dot) sequences in resource URIs. The flaw exists in versions 1.0.x before 1.0.17, 1.1.x before 1.1.0.CR5, and 1.2.x before 1.2.0.Beta3, where the web server fails to properly sanitize path traversal sequences in URLs.
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
<= 1.0.16<= 1.1.0<= 1.2.0CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Undertow installation and versionLocate the undertow-core jar file (typically named undertow-core-*.jar) in your application or JBoss installation directory. Check the filename for the version number, or inspect the META-INF/MANIFEST.MF file inside the jar for the Implementation-Version attribute.Affected if The installed version is 1.0.x at or below 1.0.16, 1.1.x at or below 1.1.0, or 1.2.x at or below 1.2.0.Beta2
-
Confirm the operating system is WindowsCheck the OS where the Undertow server is running using 'uname' on Linux/Unix or 'systeminfo' on Windows. This vulnerability only affects Windows systems.Affected if The Undertow server is running on a Windows operating system
-
Determine if static resource serving is enabledReview your Undertow configuration (often in undertow.xml, standalone.xml, or programmatic builder code) for resource handlers or servlet configurations that serve static files from the filesystem.Affected if Undertow is configured to serve static files from the filesystem, particularly using resource managers that map URIs to filesystem paths
-
Test for path traversal vulnerabilityIf the above conditions apply, send a test request to your Undertow server containing '..' sequences, such as 'GET /..\..\windows\win.ini' or similar variations, and observe if the response contains file contents outside the intended web root.Affected if Requests with '..' sequences successfully return files outside the intended web root directory
You are affected if Undertow version 1.0.16 or lower, 1.1.0 or lower, or 1.2.0.Beta2 or lower is running on Windows with static file serving enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade JBoss Undertow to version 1.0.17, 1.1.0.CR5, or 1.2.0.Beta3 or later. As a workaround on Windows, implement URL filtering to block requests containing '..' sequences.
Fix this in Undertow
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7816 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-7816 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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