dbcve.org
HadoopApplication · Apache

CVE-2017-15718

CRITICAL · 9.8 CVSS v3.0 Published 2018-01-24
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.7.3 and 2.7.4 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 · moderate confidence

The YARN NodeManager in Apache Hadoop versions 2.7.3 and 2.7.4 contains a vulnerability where passwords used by the credential store provider are inadvertently exposed or leaked to YARN Applications. This critical information disclosure vulnerability allows malicious or compromised applications to obtain sensitive credential store passwords.

MitigationUpgrade Apache Hadoop to a version beyond 2.7.4 that contains the security fix for this vulnerability, and review and rotate any credentials that may have been exposed.

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.7.3= 2.7.4

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' to determine the exact version of Hadoop installed
    Affected if The version shown is 2.7.3 or 2.7.4
  2. Verify YARN NodeManager is in use
    Check if the YARN NodeManager service is running using 'yarn node -list' or by checking for the NodeManager process
    Affected if YARN NodeManager is actively running in the environment
  3. Confirm credential store configuration exists
    Inspect Hadoop configuration files (core-site.xml, yarn-site.xml, or container-executor.cfg) for credential store provider settings such as 'hadoop.security.credential.provider.path' or custom credential provider configurations
    Affected if A credential store provider path is configured, indicating secrets/passwords are being stored externally
  4. Check for exposed credentials in application environment
    Review YARN container logs or environment variables for any plaintext passwords or credential store paths that should not be visible. Examine the contents of /proc/[pid]/environ for NodeManager processes or inspect yarn application container logs for unexpected credential exposure
    Affected if Credential store passwords or sensitive credential paths are visible in container environments where they should not be accessible

You are affected if you are running Hadoop 2.7.3 or 2.7.4 with YARN NodeManager active and a credential store provider configured, where sensitive passwords may have been inadvertently exposed to YARN applications.

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 a version beyond 2.7.4 that contains the security fix for this vulnerability, and review and rotate any credentials that may have been exposed.

Recommended fix Moderate confidence

Hadoop 2.7.5 or later (recommended: latest 2.7.x LTS or 3.x stable release)

  1. 1. Review current Hadoop deployment and confirm all NodeManager instances are running version 2.7.3 or 2.7.4
  2. 2. Plan maintenance window for upgrade - this will require service restart
  3. 3. Download Apache Hadoop 2.7.5 or later stable release (preferably latest 2.7.x LTS or 3.x release) from official Apache mirrors
  4. 4. Test upgrade in non-production environment first
  5. 5. Stop YARN NodeManager services on all affected nodes
  6. 6. Deploy new Hadoop binaries across cluster
  7. 7. Verify configuration files remain intact (especially yarn-site.xml and credential provider settings)
  8. 8. Start YARN NodeManager services
Caveat Review release notes for breaking changes between 2.7.x versions; ensure compatibility with other Hadoop ecosystem components (Hive, Spark, etc.) in your cluster

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

Fix this in Hadoop Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-15718 — 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-2017-15718 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