# CVE-2022-26612: Arbitrary file write in FileUtil#unpackEntries on Windows

> An attacker can write arbitrary files outside the intended directory on Windows by exploiting symlink handling during TAR extraction in Apache Hadoop.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gx2c-fvhc-ph4j

## What is CVE-2022-26612?

CVE-2022-26612 is a critical path traversal vulnerability in Apache Hadoop, published on 7 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2022-26612?

6 open source packages ship an affected version, including org.apache.hadoop:hadoop-common. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.hadoop:hadoop-common` | Maven | All versions | 2.10.2 |
| `org.apache.hadoop:hadoop-common` | Maven | All versions | 2.10.2 |
| `org.apache.hadoop:hadoop-common` | Maven | From 3.2.0 | 3.2.3 |
| `org.apache.hadoop:hadoop-common` | Maven | From 3.2.0 | 3.2.3 |
| `org.apache.hadoop:hadoop-common` | Maven | From 3.3.0 | 3.3.3 |
| `org.apache.hadoop:hadoop-common` | Maven | From 3.3.0 | 3.3.3 |

Products: Apache Hadoop.

## How do I fix CVE-2022-26612?

Upgrade org.apache.hadoop:hadoop-common to a fixed version for your release line: 2.10.2, 3.2.3 or 3.3.3.

## Is CVE-2022-26612 being exploited?

There is no known exploitation of CVE-2022-26612 in the wild and no public exploit code.

## Other vulnerabilities in Apache Hadoop

- [CVE-2022-25168](https://insights.sbomify.com/CVE-2022-25168/): Command injection in org.apache.hadoop.fs.FileUtil.unTarUsingTar (critical 9.8)
- [CVE-2021-37404](https://insights.sbomify.com/CVE-2021-37404/): Heap buffer overflow in libhdfs native library (critical 9.8)
- [CVE-2019-17195](https://insights.sbomify.com/CVE-2019-17195/): Improper Check for Unusual or Exceptional Conditions in Connect2id Nimbus JOSE+JWT (critical 9.8)
- [CVE-2017-15718](https://insights.sbomify.com/CVE-2017-15718/): Exposure of Sensitive Information in Hadoop (critical 9.8)
- [CVE-2012-4449](https://insights.sbomify.com/CVE-2012-4449/): Use of a Broken or Risky Cryptographic Algorithm in Apache Hadoop (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26612 and fix it if it is affected.

What it is: CVE-2022-26612 is a critical path traversal vulnerability in Apache Hadoop, published on 7 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-26612 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.hadoop:hadoop-common (Maven): affected all versions; fixed in 2.10.2
- org.apache.hadoop:hadoop-common (Maven): affected all versions; fixed in 2.10.2
- org.apache.hadoop:hadoop-common (Maven): affected from 3.2.0; fixed in 3.2.3
- org.apache.hadoop:hadoop-common (Maven): affected from 3.2.0; fixed in 3.2.3
- org.apache.hadoop:hadoop-common (Maven): affected from 3.3.0; fixed in 3.3.3
- org.apache.hadoop:hadoop-common (Maven): affected from 3.3.0; fixed in 3.3.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-26612/ (Markdown: https://insights.sbomify.com/CVE-2022-26612/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-26612
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-26612
- OSV: https://osv.dev/vulnerability/CVE-2022-26612

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-26612/
Summaries are generated and may contain mistakes; the official description above is the record.