# CVE-2022-25168: Command injection in org.apache.hadoop.fs.FileUtil.unTarUsingTar > Attackers can inject arbitrary shell commands via unescaped file names in Hadoop's untar utility, potentially leading to remote code execution. - **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:** 4 Aug 2022 - **Updated:** 3 Aug 2024 - **Also known as:** GHSA-8wm5-8h9c-47pc ## What is CVE-2022-25168? CVE-2022-25168 is a critical command injection vulnerability in Apache Hadoop, published on 4 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Apache Hadoop's FileUtil.unTar(File, File) API does not escape the input file name before being passed to the shell. An attacker can inject arbitrary commands. This is only used in Hadoop 3.3 InMemoryAliasMap.completeBootstrapTransfer, which is only ever run by a local user. It has been used in Hadoop 2.x for yarn localization, which does enable remote code execution. It is used in Apache Spark, from the SQL command ADD ARCHIVE. As the ADD ARCHIVE command adds new binaries to the classpath, being able to execute shell scripts does not confer new permissions to the caller. SPARK-38305. "Check existence of file before untarring/zipping", which is included in 3.3.0, 3.1.4, 3.2.2, prevents shell commands being executed, regardless of which version of the hadoop libraries are in use. Users should upgrade to Apache Hadoop 2.10.2, 3.2.4, 3.3.3 or upper (including HADOOP-18136). Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command) ## Which versions are affected by CVE-2022-25168? 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 | From 2.0.0 | 2.10.2 | | `org.apache.hadoop:hadoop-common` | Maven | From 2.0.0 | 2.10.2 | | `org.apache.hadoop:hadoop-common` | Maven | From 3.0.0-alpha | 3.2.4 | | `org.apache.hadoop:hadoop-common` | Maven | From 3.0.0-alpha | 3.2.4 | | `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-25168? Upgrade org.apache.hadoop:hadoop-common to a fixed version for your release line: 2.10.2, 3.2.4 or 3.3.3. ## Is CVE-2022-25168 being exploited? There is no known exploitation of CVE-2022-25168 in the wild and no public exploit code. ## Other vulnerabilities in Apache Hadoop - [CVE-2021-37404](https://insights.sbomify.com/CVE-2021-37404/): Heap buffer overflow in libhdfs native library (critical 9.8) - [CVE-2022-26612](https://insights.sbomify.com/CVE-2022-26612/): Arbitrary file write in FileUtil#unpackEntries on Windows (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-25168 and fix it if it is affected. What it is: CVE-2022-25168 is a critical command injection vulnerability in Apache Hadoop, published on 4 Aug 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-25168 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.hadoop:hadoop-common (Maven): affected from 2.0.0; fixed in 2.10.2 - org.apache.hadoop:hadoop-common (Maven): affected from 2.0.0; fixed in 2.10.2 - org.apache.hadoop:hadoop-common (Maven): affected from 3.0.0-alpha; fixed in 3.2.4 - org.apache.hadoop:hadoop-common (Maven): affected from 3.0.0-alpha; fixed in 3.2.4 - 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-25168/ (Markdown: https://insights.sbomify.com/CVE-2022-25168/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-25168 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-25168 - OSV: https://osv.dev/vulnerability/CVE-2022-25168 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-25168/ Summaries are generated and may contain mistakes; the official description above is the record.