LiveActive security incident?Get immediate response
CVE Record

CVE-2016-6811: In Apache Hadoop 2.x before 2.7.4, a user who can escalate to yarn user can possibly run arbitrary commands...

In Apache Hadoop 2.x before 2.7.4, a user who can escalate to yarn user can possibly run arbitrary commands as root user.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw affects Apache Hadoop 2.x versions before 2.7.4. If an attacker or insider can first become the Hadoop yarn user, they may be able to execute arbitrary commands as root. That makes it a serious privilege escalation risk on affected Hadoop infrastructure, but the public bundle does not show active exploitation.

Executive priority

Treat this as a high-priority legacy infrastructure risk if Hadoop 2.x remains in use. The business concern is local privilege escalation to root on data-processing nodes, not internet-wide exploitation based on the supplied evidence.

Technical view

CVE-2016-6811 is a Hadoop privilege escalation issue. The stated affected range is Apache Hadoop 2.x before 2.7.4. The prerequisite is the ability to escalate to, or otherwise operate as, the yarn user; from there, arbitrary command execution as root may be possible. No CVSS, CWE, or detailed root cause is provided in the supplied sources.

Likely exposure

Exposure is most likely on legacy Apache Hadoop 2.x clusters running versions earlier than 2.7.4, especially multi-user environments where users may reach the yarn account or administer YARN-related services.

Exploitation context

The sources do not report known active exploitation, and CISA KEV status is false in the bundle. Exploitation appears to require prior access sufficient to become the yarn user, so this is more likely a post-access escalation risk than an initial intrusion vector.

Researcher notes

The public data is sparse: no CVSS vector, CWE, proof details, or exploit confirmation are included. Analysis should stay anchored to the Apache mailing-list advisory and CVE record. Validate exposure by version and yarn-user reachability, then confirm remediation against Apache or downstream vendor notes.

Mitigation direction

  • Identify Hadoop 2.x deployments and confirm exact versions.
  • Upgrade affected Hadoop 2.x systems to 2.7.4 or later where supported.
  • Review the Apache advisory for vendor-specific guidance.
  • Restrict access paths to the yarn user pending remediation.
  • Apply downstream distribution fixes if using packaged Hadoop.

Validation and detection

  • Inventory Hadoop clusters and compare versions against 2.x before 2.7.4.
  • Review account controls for users able to become yarn.
  • Check host logs for unexpected root commands tied to Hadoop/YARN activity.
  • Confirm patched or upgraded nodes are consistent across the cluster.
  • Document any unsupported legacy Hadoop instances as exceptions.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-6811 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.