~ / search / GHSA-gx2c-fvhc-ph4j

GHSA-gx2c-fvhc-ph4j

Path traversal in Hadoop

Source: GitHub Advisory Database (reviewed) Critical CVE-2022-26612

Packages

EcosystemPackageAffectedFixed in
Maven org.apache.hadoop:hadoop-common >= 3.2.0, < 3.2.3 3.2.3
Maven org.apache.hadoop:hadoop-common < 2.10.2 2.10.2
Maven org.apache.hadoop:hadoop-common >= 3.3.0, < 3.3.3 3.3.3

Details

As written in the advisory (Markdown source, shown as plain text).

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 2.10.2, 3.2.3, 3.3.3, and 3.4.0.

References

External links from the advisory. They lead to third-party sites.