CVE-2014-7816 Improper Limitation of a Pathname to a Restricted Directory in JBoss Undertow
Remote attackers can read arbitrary files on Windows systems running JBoss Undertow via directory traversal in resource URIs.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2014-7816?
CVE-2014-7816 is a medium-severity path traversal vulnerability in n/a, published on 1 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Directory 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.
Weakness: CWE-22
Which versions are affected by CVE-2014-7816?
6 open source packages ship an affected version, including io.undertow:undertow-core. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
io.undertow:undertow-core Maven | From 1.0.0 | 1.0.17 |
io.undertow:undertow-core Maven | From 1.0.0 | 1.0.17 |
io.undertow:undertow-core Maven | From 1.1.0.Beta1 | 1.1.0.CR5 |
io.undertow:undertow-core Maven | From 1.1.0.Beta1 | 1.1.0.CR5 |
io.undertow:undertow-core Maven | From 1.2.0.Beta1 | 1.2.0.Beta3 |
io.undertow:undertow-core Maven | From 1.2.0.Beta1 | 1.2.0.Beta3 |
Products include Redhat Undertow.
How do I fix CVE-2014-7816?
Upgrade io.undertow:undertow-core to a fixed version for your release line: 1.0.17, 1.1.0.CR5 or 1.2.0.Beta3.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2014-7816 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-7816 exists.
Public exploit code: 1 Metasploit module and 1 proofs of concept on GitHub.
Other vulnerabilities in n/a
Sources
Also known as GHSA-h6p6-fc4w-cqhx.