Apache Software Foundation Hadoop 3.3.2 -

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:apache:hadoop:3.3.2:-:*:*:*:*:*:*

part: a version: 3.3.2 update: -

VendorApache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95)
ProductHadoop (69f26508-0b29-5671-ae34-5898b6ed48d6)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:apache/hadoop purl2cpe 2026-06-01 10:14:26.775602
pkg:dokcer/apache/hadoop purl2cpe 2026-06-01 10:14:26.775603
pkg:github/apache/hadoop purl2cpe 2026-06-01 10:14:26.775605
pkg:maven/org.apache.hadoop/hadoop-core purl2cpe 2026-06-01 10:14:26.775606
pkg:rpm/fedora/hadoop purl2cpe 2026-06-01 10:14:26.775607
pkg:rpm/opensuse/hadoop purl2cpe 2026-06-01 10:14:26.775609

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2022-26612 vulnerable 2026-06-08 05:41:52.602473 Arbitrary file write in FileUtil#unpackEntries on Windows
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
Published: 2022-04-07T18:20:12.000Z
Updated: 2024-08-03T05:11:43.529Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.