CVE-2022-26612
A subsequent TAR entry may extract an arbitrary file into the external directory using the symlink name.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (4.24%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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
- CVSS 3.1
- 9.8 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 4.24% probability · 90th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-59
- Affected
- apache/hadoop
- Source
- security@apache.org
References
- https://lists.apache.org/thread/hslo7wzw2449gv1jyjk8g6ttd7935fyzExploit, Vendor Advisory
- https://security.netapp.com/advisory/ntap-20220519-0004/Third Party Advisory
- https://lists.apache.org/thread/hslo7wzw2449gv1jyjk8g6ttd7935fyzExploit, Vendor Advisory
- https://security.netapp.com/advisory/ntap-20220519-0004/Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.