Skip to content
Fencer Intel
high 7.4

CVE-2018-11767 json

Improper Privilege Management in org.apache.hadoop:hadoop-main

published 7y ago modified 4mo ago also GHSA-5cf4-jqwp-584g , EUVD-2019-0370

cvss
7.4
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.7%
EPSS 3.7% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.hadoop:hadoop-main 2.7.7, 2.8.5, 2.9.2

Is CVE-2018-11767 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-11767 updated cvss 5.0

hadoop: Apache Hadoop KMS ACL regression

  • Red Hat Fuse 7 hadoop hadoop
    affected: no fix planned “Will not fix”
  • Red Hat JBoss Fuse 6 hadoop hadoop
    affected: no fix planned “Out of support scope”
  • Red Hat Storage 3 rhs-hadoop
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.73% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.4 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:N/A:P
GitHub 3.0 7.4 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.hadoop:hadoop-main
>=2.7.5, <2.7.7
>=2.8.3, <2.8.5
>=2.9.0, <2.9.2
2.7.7
2.8.5
2.9.2

Affected products

  • n/a Apache Hadoop

Classification

Weakness
  • CWE-269 Improper Privilege Management

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.