Undertow: undertow: pathresourcemanager safepaths check allows sibling-directory symlink traversal
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
A flaw was found in the PathResourceManager component of the Undertow web server. This component is responsible for serving static files from the file system. The issue occurs because the mechanism used to verify if a symbolic link points to a safe location only checks if the target path starts with a specific string, without ensuring it matches a full directory name. This could allow an attacker to access files in a sibling directory if that directorys name starts with the same characters as an authorized safe directory.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
- First seen by cve.now
Affected versions
- undertow-servlet
Version range not reported
- pki-core:10.6/resteasy
Version range not reported
- pki-deps:10.6/resteasy
Version range not reported
- resteasy
Version range not reported
- undertow-servlet
Version range not reported
- jboss-eap-7/eap74-els-openjdk11-openshift-rhel8
Version range not reported
- jboss-eap-7/eap74-els-openjdk17-openshift-rhel8
Version range not reported
- jboss-eap-7/eap74-els-openjdk8-openshift-rhel8
Version range not reported
- undertow-servlet
Version range not reported
- undertow-servlet
Version range not reported
- undertow-servlet
Version range not reported
- undertow-servlet
Version range not reported