Arbitrary file write in FileUtil#unpackEntries on Windows
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 4%. Fixed in 3.2.3.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Apache Software Foundation | <3.2.3, =3.3.1, =3.3.2 | 3.2.3 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket