Hadoop symlink vulnerability

published 2019-10-28 7 y ago modified 2026-06-16 4 mo ago also GHSA-v5c9-98f7-2h54 , EUVD-2022-1832

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.7%; EPSS 2.7% chance of exploitation in 30 days, percentile 85%
public exploits: 0; none known

Hadoop 1.0.3 contains a symlink vulnerability.

Patch / fix

fixed in 1

maven org.apache.hadoop:hadoop-main 1.0.4

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-2945 updated 2026-11-05 cvss 5.3

hadoop: symlink vulnerability in conf/hadoop-env.sh

Red Hat Satellite 5 hadoop-common, spacewalk-search
affected: no fix planned “Out of support scope”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.67% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

seclists.org https://seclists.org/fulldisclosure/2012/Jul/3 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	org.apache.hadoop:hadoop-main	<1.0.4	1.0.4

Classification

Weakness

CWE-59 Improper Link Resolution Before File Access
CWE-377 DEPRECATED: Insecure Temporary File

References

seclists.org /fulldisclosure/2012/Jul/3
web, exploit, mailing-list, third-party-advisory
security-tracker.debian.org /tracker/CVE-2012-2945
web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2012-2945
advisory
bugs.debian.org /cgi-bin/bugreport.cgi?bug=535861
web
github.com /apache/hadoop
package

Sources

CVE List CVE-2012-2945
GitHub Advisory GHSA-v5c9-98f7-2h54
NVD CVE-2012-2945

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary