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
References
Link | Resource |
---|---|
https://lists.apache.org/thread/hslo7wzw2449gv1jyjk8g6ttd7935fyz | Exploit Vendor Advisory |
https://security.netapp.com/advisory/ntap-20220519-0004/ | Third Party Advisory |
Configurations
Configuration 1 (hide)
AND |
|
History
08 Aug 2023, 14:21
Type | Values Removed | Values Added |
---|---|---|
CWE | CWE-59 |
Information
Published : 2022-04-07 19:15
Updated : 2024-02-28 19:09
NVD link : CVE-2022-26612
Mitre link : CVE-2022-26612
CVE.ORG link : CVE-2022-26612
JSON object : View
Products Affected
microsoft
- windows
apache
- hadoop
CWE
CWE-59
Improper Link Resolution Before File Access ('Link Following')