Not rated
CVE-2022-26612 In Apache Hadoop, The unTar function uses unTarUsingJava function on Windows and the built-in tar utility on Unix and…
Description
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
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Apache Hadoop 3.4 | earliest → < 3.4 | 3.4 |
| Apache Hadoop 3.3 | 3.3.1 → 3.3.2 | No fix stated |
| Apache Hadoop 3.2 | earliest → < 3.2.3 | 3.2.3 |
References
- lists.apache.org lists.apache.org
- security.netapp.com security.netapp.com
Timeline
- Published
- Last modified
Other CVEs of Apache Hadoop
The 18 CVEs of Apache Hadoop →
CVE-2024-23454
Apache Hadoop’s RunJar.run() does not set permissions for temporary directory by default
Not rated
CVE-2023-26031
Relative library resolution in linux container-executor binary in Apache Hadoop 3.3.1-3.3.4 on Linux allows local user…
Not rated
CVE-2021-25642
ZKConfigurationStore which is optionally used by CapacityScheduler of Apache Hadoop YARN deserializes data obtained from…
Not rated
CVE-2022-25168
Apache Hadoop's FileUtil.unTar(File, File) API does not escape the input file name before being passed to the shell
Not rated