Arbitrary file write in FileUtil#unpackEntries on Windows
- 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
- Fix
- Fixed in 3.2.3, 2.10.2, 3.3.3
- 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
Summary
In Apache Hadoop, The unTar function uses unTarUsingJava function on Windows and the built-in tar utility on Unix and other OSes. As a result, a TAR entry may create a symlink under the expected extraction directory which points to an external directory. A subsequent TAR entry may extract an arbitrary file into the external directory using the symlink name. This however would be caught by the same targetDirPath check on Unix because of the getCanonicalPath call. However on Windows, getCanonicalPath doesn't resolve symbolic links, which bypasses the check. unpackEntries during TAR extraction follows symbolic links which allows writing outside expected base directory on Windows. This was addressed in Apache Hadoop 3.2.3
Timeline
- CVE published
- Record last updated
Affected versions
- Apache Software Foundation Apache Hadoop
fixed in 3.2.3
- org.apache.hadoop:hadoop-commonMaven
From 3.2.0 · fixed in 3.2.3
- org.apache.hadoop:hadoop-commonMaven
fixed in 2.10.2
- org.apache.hadoop:hadoop-commonMaven
From 3.3.0 · fixed in 3.3.3