Skip to content

Apache Hadoop argument injection vulnerability

Critical severity GitHub Reviewed Published Aug 5, 2022 to the GitHub Advisory Database • Updated Jul 4, 2023

Package

maven org.apache.hadoop:hadoop-common (Maven)

Affected versions

>= 2.0.0, < 2.10.2
>= 3.0.0-alpha, < 3.2.4
>= 3.3.0, < 3.3.3

Patched versions

2.10.2
3.2.4
3.3.3

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).

References

Published by the National Vulnerability Database Aug 4, 2022
Published to the GitHub Advisory Database Aug 5, 2022
Reviewed Aug 11, 2022
Last updated Jul 4, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.564%
(78th percentile)

Weaknesses

CVE ID

CVE-2022-25168

GHSA ID

GHSA-8wm5-8h9c-47pc

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.