Summary
Apache Hadoop argument injection vulnerability
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).
Impact
Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.
CVE-2022-25168 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.10.2, 3.2.4, 3.3.3); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.apache.hadoop:hadoop-common to 2.10.2 or later; org.apache.hadoop:hadoop-common to 3.2.4 or later; org.apache.hadoop:hadoop-common to 3.3.3 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2022-25168? CVE-2022-25168 is a critical-severity OS command injection vulnerability in org.apache.hadoop:hadoop-common (maven), affecting versions >= 2.0.0, < 2.10.2. It is fixed in 2.10.2, 3.2.4, 3.3.3. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
- How severe is CVE-2022-25168? CVE-2022-25168 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.apache.hadoop:hadoop-common are affected by CVE-2022-25168? org.apache.hadoop:hadoop-common (maven) versions >= 2.0.0, < 2.10.2 is affected.
- Is there a fix for CVE-2022-25168? Yes. CVE-2022-25168 is fixed in 2.10.2, 3.2.4, 3.3.3. Upgrade to this version or later.
- Is CVE-2022-25168 exploitable, and should I be worried? Whether CVE-2022-25168 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-25168 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-25168?
- Upgrade
org.apache.hadoop:hadoop-commonto 2.10.2 or later - Upgrade
org.apache.hadoop:hadoop-commonto 3.2.4 or later - Upgrade
org.apache.hadoop:hadoop-commonto 3.3.3 or later
- Upgrade