CVE-2018-11767 — hadoop-main
HIGHCVE-2018-11767 is a high-severity (CVSS 7.4) Improper Privilege Management 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.
Improper Privilege Management in org.apache.hadoop:hadoop-main
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2018-11767 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 2.9.0 to 2.9.1, 2.8.3 to 2.8.4, 2.7.5 to 2.7.6, KMS blocking users or granting access to users incorrectly, if the system uses non-default groups mapping mechanisms.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.hadoop:hadoop-main | ≥ 2.7.5&&< 2.7.7 | 2.7.7org.apache.hadoop:hadoop-main:2.7.7 |
| ☕Maven | org.apache.hadoop:hadoop-main | ≥ 2.8.3&&< 2.8.5 | 2.8.5org.apache.hadoop:hadoop-main:2.8.5 |
| ☕Maven | org.apache.hadoop:hadoop-main | ≥ 2.9.0&&< 2.9.2 | 2.9.2org.apache.hadoop:hadoop-main:2.9.2 |
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.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-11767 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2018-11767 in your dependencies?
Find it across Maven, including transitive dependencies.