HadoopApplication · Apache
CVE-2014-3627
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 · uneditedThe YARN NodeManager daemon in Apache Hadoop 0.23.0 through 0.23.11 and 2.x before 2.5.2, when using Kerberos authentication, allows remote cluster users to change the permissions of certain files to world-readable via a symlink attack in a public tar archive, which is not properly handled during localization, related to distributed cache.
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 Apache Hadoop YARN NodeManager versions 0.23.0-0.23.11 and 2.x before 2.5.2, when Kerberos authentication is enabled, a symlink attack in distributed cache localization allows remote cluster users to change permissions of arbitrary files to world-readable. The vulnerability exists because the NodeManager does not properly validate symlinks within tar archives during the resource localization process.
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
= 0.23.0= 0.23.1= 0.23.3= 0.23.4= 0.23.5= 0.23.6= 0.23.7= 0.23.8= 0.23.9= 0.23.10= 0.23.11= 2.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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 Hadoop YARN NodeManager installationLocate the Hadoop installation and confirm NodeManager is present by checking for the yarn nodemanager process or the yarn-site.xml configuration file in the Hadoop conf directoryAffected if NodeManager is installed and running
-
Check installed Hadoop versionRun 'hadoop version' or check the hadoop-common JAR manifest to determine the exact version numberAffected if Version is 0.23.0 through 0.23.11, or 2.0.0 through 2.5.1 (any 2.x version before 2.5.2)
-
Verify Kerberos authentication is enabledInspect yarn-site.xml for yarn.nodemanager.keytab and yarn.resourcemanager.principal settings, or check if kinit has been used to obtain Kerberos tickets for YARN operationsAffected if Kerberos authentication is enabled for YARN (the vulnerability requires Kerberos to be active)
-
Confirm distributed cache localization is in useReview application logs for localized resources or check if applications submit tar archives (.tar, .tar.gz) to the distributed cacheAffected if Users submit tar archives that get localized to node local directories
All four conditions must be true: running a vulnerable Hadoop version (0.23.0-0.23.11 or 2.0.0-2.5.1), with Kerberos enabled, and using distributed cache localization with tar archives.
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 Apache Hadoop to version 0.23.12+, 2.5.2+, or later patched versions. Additionally, ensure proper filesystem permissions and consider enabling ACLs on the local directories used for container localization.
Fix this in Hadoop
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3627 — 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-2014-3627 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