Exposure of Sensitive Information to an Unauthorized Actor in HadoopGHSA-v569-g72v-q434
HIGHGHSA-v569-g72v-q434 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.apache.hadoop:hadoop-main. A fix is available for org.apache.hadoop:hadoop-main — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-v569-g72v-q434 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.apache.hadoop:hadoop-main☕org.apache.hadoop:hadoop-main☕org.apache.hadoop:hadoop-mainReal-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 3.0.0-alpha1 to 3.0.0, 2.9.0, 2.8.0 to 2.8.3, and 2.5.0 to 2.7.5, HDFS exposes extended attribute key/value pairs during listXAttrs, verifying only path-level search access to the directory rather than path-level read permission to the referent.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.hadoop:hadoop-main | all versions | 2.7.6org.apache.hadoop:hadoop-main:2.7.6 |
| ☕Maven | org.apache.hadoop:hadoop-main | ≥ 2.8.0&&< 2.8.4 | 2.8.4org.apache.hadoop:hadoop-main:2.8.4 |
| ☕Maven | org.apache.hadoop:hadoop-main | ≥ 2.9.0&&< 2.9.1 | 2.9.1org.apache.hadoop:hadoop-main:2.9.1 |
Affected Products
hadoopapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.hadoop:hadoop-main, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.hadoop:hadoop-main to 2.7.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v569-g72v-q434 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
If a file contains sensitive data in extended attributes, users and admins need to change the permission to prevent others from listing the directory which contains the file.Source: Red Hat security advisory for GHSA-v569-g72v-q434 (CC BY 4.0)
Frequently Asked Questions
Is GHSA-v569-g72v-q434 in your dependencies?
Find it across Maven, including transitive dependencies.