How severe is GHSA-h24p-qwf4-84q8?

GHSA-h24p-qwf4-84q8 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-h24p-qwf4-84q8?

GHSA-h24p-qwf4-84q8 affects the following packages: org.apache.hadoop:hadoop-common (Maven), org.apache.hadoop:hadoop-common (Maven). Ecosystems affected: Maven.

How do I fix GHSA-h24p-qwf4-84q8?

Update org.apache.hadoop:hadoop-common to 2.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h24p-qwf4-84q8 is resolved across your whole dependency graph.

How do I detect GHSA-h24p-qwf4-84q8 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.hadoop:hadoop-common. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-h24p-qwf4-84q8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-h24p-qwf4-84q8?

O3 pinpoints whether GHSA-h24p-qwf4-84q8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-h24p-qwf4-84q8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h24p-qwf4-84q8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-h24p-qwf4-84q8?

GHSA-h24p-qwf4-84q8 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-h24p-qwf4-84q8 published, and has it been updated?

GHSA-h24p-qwf4-84q8 was published on May 17, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

GHSA-h24p-qwf4-84q8

HIGH

GHSA-h24p-qwf4-84q8 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in org.apache.hadoop:hadoop-common. O3 Security confirms whether GHSA-h24p-qwf4-84q8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Apache Hadoop's LinuxContainerExecutor runs docker commands as root with insufficient input validation

Also known asCVE-2017-7669

Published

May 17, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

☕org.apache.hadoop:hadoop-common☕org.apache.hadoop:hadoop-common

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

In Apache Hadoop 2.8.0, 3.0.0-alpha1, and 3.0.0-alpha2, the LinuxContainerExecutor runs docker commands as root with insufficient input validation. When the docker feature is enabled, authenticated users can run commands as root. This issue is fixed in versions 2.8.1 and 3.0.0-alpha3.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.hadoop:hadoop-common`	all versions	2.8.1
☕Maven	`org.apache.hadoop:hadoop-common`	≥ 3.0.0-alpha1&&< 3.0.0-alpha3	3.0.0-alpha3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.hadoop:hadoop-common. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.hadoop:hadoop-common to 2.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h24p-qwf4-84q8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-h24p-qwf4-84q8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-h24p-qwf4-84q8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-h24p-qwf4-84q8 in your dependencies?

O3 detects GHSA-h24p-qwf4-84q8 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works