cve.bz

CVE-2014-3627 apache hadoop: Link Following

no score yetEPSS 3.0%Fix available

apache hadoop: no CVSS score yet. EPSS 3.0% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.hadoop:hadoop-client 1.0.1, 2.5.2.

On this page
The 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.
EPSS
3.0% (unchanged from 3.0% a week ago; 3.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 88th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • org.apache.hadoop:hadoop-client (Maven): fixed in 1.0.1, 2.5.2

Ask an AI about this CVE

Show the promptExplain CVE-2014-3627 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2014-3627?via=ask-ai-copy and https://cve.bz/cve/CVE-2014-3627?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2014-3627 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
apache:hadoop0.23.0
apache:hadoop0.23.1
apache:hadoop0.23.3
apache:hadoop0.23.4
apache:hadoop0.23.5
apache:hadoop0.23.6
apache:hadoop0.23.7
apache:hadoop0.23.8
apache:hadoop0.23.9
apache:hadoop0.23.10
apache:hadoop0.23.11
apache:hadoop2.0.0:alpha
apache:hadoop2.0.1:alpha
apache:hadoop2.0.2:alpha
apache:hadoop2.0.3:alpha
apache:hadoop2.0.4:alpha
apache:hadoop2.0.5:alpha
apache:hadoop2.0.6:alpha
apache:hadoop2.1.0:beta
apache:hadoop2.1.1:beta
apache:hadoop2.2.0
apache:hadoop2.3.0
apache:hadoop2.4.0
apache:hadoop2.4.1
apache:hadoop2.5.0
apache:hadoop2.5.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jpmf-8cj2-595gMavenorg.apache.hadoop:hadoop-client>=0.23.0 <1.0.11.0.1
GHSA-jpmf-8cj2-595gMavenorg.apache.hadoop:hadoop-client>=2.0.0 <2.5.22.5.2

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This issue may affect the versions of hadoop as shipped with Red Hat Enterprise Virtualization Manager. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

ProductPackageStateAdvisory
Red Hat Enterprise Virtualization 3jasperreports-server-proUnder investigation

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2014-3627.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON