HadoopApplication · Apache
CVE-2017-3166
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 · uneditedIn Apache Hadoop versions 2.6.1 to 2.6.5, 2.7.0 to 2.7.3, and 3.0.0-alpha1, if a file in an encryption zone with access permissions that make it world readable is localized via YARN's localization mechanism, that file will be stored in a world-readable location and can be shared freely with any application that requests to localize that file.
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 confidenceIn affected Hadoop versions, when YARN localizes a file from an encryption zone that has world-readable permissions, the file gets stored in a world-readable local directory. This bypasses encryption zone protections, allowing any application on the node to access the localized file without authorization.
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
= 2.6.1= 2.6.2= 2.6.3= 2.6.4= 2.6.5= 2.7.0= 2.7.1= 2.7.2= 2.7.3= 3.0.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Hadoop versionRun 'hadoop version' or check the Hadoop distribution package version. Compare against the affected versions: 2.6.1-2.6.5, 2.7.0-2.7.3, and 3.0.0Affected if The installed version matches any of the affected versions listed
-
Verify YARN is enabledCheck if YARN (Yet Another Resource Negotiator) is configured and running. Look for ResourceManager and NodeManager processes using 'jps' command or check yarn-site.xml for yarn.resourcemanager.address and yarn.nodemanager.aux-servicesAffected if YARN is running and the Hadoop version is affected
-
Confirm encryption zones are configuredCheck for HDFS encryption zones using 'hdfs crypto -listZones' command. Also look for encryption zone keys configured in core-site.xml (hadoop.security.key.provider.path)Affected if Encryption zones exist and the Hadoop version is affected
-
Inspect localized file permissions in YARN local directoriesCheck the YARN local directory (configured via yarn.nodemanager.local-dirs, typically /tmp/yarn or /var/tmp/yarn). Run 'ls -la' on these directories and inspect permissions on localized files from encryption zonesAffected if Files in YARN local directories have world-readable permissions (chmod 644 or 777) when they originated from encryption zones
A user is affected if they run an affected Hadoop version with YARN enabled, use HDFS encryption zones, and have files localized to YARN local directories that became world-readable.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade Hadoop to a patched version and audit encryption zones to remove world-readable permissions from sensitive files before localization.
Fix this in Hadoop
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2017-3166 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-3166 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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