dbcve.org
HadoopApplication · Apache

CVE-2016-3086

CRITICAL · 9.8 CVSS v3.0 Published 2017-09-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The YARN NodeManager in Apache Hadoop 2.6.x before 2.6.5 and 2.7.x before 2.7.3 can leak the password for credential store provider used by the NodeManager to YARN Applications.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The YARN NodeManager in Apache Hadoop versions 2.6.x before 2.6.5 and 2.7.x before 2.7.3 contains a vulnerability where passwords used by the credential store provider are inadvertently leaked to YARN Applications. This exposes sensitive credential information to potentially untrusted application code.

MitigationUpgrade Apache Hadoop to version 2.6.5, 2.7.3, or later to patch the credential leakage vulnerability in the NodeManager component.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HadoopApplication
Affected:= 2.6.0= 2.6.1= 2.6.2= 2.6.3= 2.6.4= 2.7.0= 2.7.1= 2.7.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Hadoop version
    Run 'hadoop version' on the NodeManager host to obtain the exact version number
    Affected if Version is 2.6.0 through 2.6.4, or 2.7.0 through 2.7.2 (falls within the affected ranges)
  2. Confirm YARN NodeManager is deployed
    Check if the NodeManager process is running: look for 'NodeManager' in process list (ps aux | grep NodeManager) or check yarn-site.xml for yarn.nodemanager.address configuration
    Affected if NodeManager is running and version is in the affected range
  3. Verify credential store provider usage
    Examine yarn-site.xml and core-site.xml for credential provider configurations such as 'hadoop.security.credential.provider.path' or similar credential store settings
    Affected if A credential store provider is configured with passwords and NodeManager version is affected

Environment is affected if running a Hadoop version between 2.6.0-2.6.4 or 2.7.0-2.7.2 with YARN NodeManager enabled and a credential store provider configured with passwords.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache Hadoop to version 2.6.5, 2.7.3, or later to patch the credential leakage vulnerability in the NodeManager component.

Recommended fix High confidence

Hadoop 2.6.5 (minimum fixed release for 2.6.x branch)

  1. 1. Review current Hadoop deployment to confirm all NodeManager instances running affected versions (2.6.0-2.6.3)
  2. 2. Schedule maintenance window for Hadoop cluster update
  3. 3. Download Apache Hadoop 2.6.5 or later from official Apache mirrors (hadoop.apache.org)
  4. 4. Upgrade Hadoop cluster components in following order: first non-critical nodes, then NameNode/ResourceManager, finally all NodeManagers
  5. 5. Verify credential store provider configuration does not expose passwords in plain text
  6. 6. Restart YARN services and validate applications run without errors
  7. 7. Confirm the password leak vulnerability is resolved by testing that YARN applications no longer receive credential store passwords
Caveat Review release notes for 2.6.5 for any compatibility changes; test critical YARN applications in non-production environment before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hadoop Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-3086 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-3086 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data