cve.bz

CVE-2018-8009 apache hadoop: Path traversal

8.8 highExploit referenceEPSS 6.7%Fix available

High (8.8) in apache hadoop. EPSS 6.7% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.hadoop:hadoop-main 2.7.7, 2.8.5, 2.9.2.

On this page
Apache Hadoop 3.1.0, 3.0.0-alpha to 3.0.2, 2.9.0 to 2.9.1, 2.8.0 to 2.8.4, 2.0.0-alpha to 2.7.6, 0.23.0 to 0.23.11 is exploitable via the zip slip vulnerability in places that accept a zip file.

Severity

CVSS 3.0

8.8 high
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
6.7% (unchanged from 6.7% a week ago; 6.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 94th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2018-8009 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2018-8009?via=ask-ai-copy and https://cve.bz/cve/CVE-2018-8009?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-2018-8009 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:hadoopfrom 0.23.0 through 0.23.11
apache:hadoopfrom 2.0.0 through 2.7.6
apache:hadoopfrom 2.8.0 through 2.8.4
apache:hadoopfrom 2.9.0 through 2.9.1
apache:hadoopfrom 3.0.0 through 3.0.2
apache:hadoop2.0.0:alpha
apache:hadoop3.0.0:alpha1
apache:hadoop3.0.0:alpha2
apache:hadoop3.0.0:alpha3
apache:hadoop3.0.0:alpha4
apache:hadoop3.0.0:beta1
apache:hadoop3.1.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6x48-j4x4-cqw3Mavenorg.apache.hadoop:hadoop-main>=3.1.0 <3.1.13.1.1
GHSA-6x48-j4x4-cqw3Mavenorg.apache.hadoop:hadoop-main>=3.0.0 <3.0.33.0.3
GHSA-6x48-j4x4-cqw3Mavenorg.apache.hadoop:hadoop-main>=2.9.0 <2.9.22.9.2
GHSA-6x48-j4x4-cqw3Mavenorg.apache.hadoop:hadoop-main>=2.8.0 <2.8.52.8.5
GHSA-6x48-j4x4-cqw3Mavenorg.apache.hadoop:hadoop-main<2.7.72.7.7

Red Hat

Red Hat rates this Important.

Red Hat's statement

This issue did not affect the versions of rhs-hadoop as shipped with Red Hat Gluster Storage 3. For JBoss Fuse 6.3 and 7 standalone, while they ship vulnerable artifact via camel-hbase, camel-hdfs2 (fuse 6.3) and camel-hdfs2 (fuse 7), there's no invocation on the flawed code that could lead to an unzip operation. So fuse 6.3, 7 standalone are not affected. However FIS 2.0 and Fuse 7 on OpenShift ship vulnerable artifact via maven BOM, so setting fuse as affected for this reason.

ProductPackageStateAdvisory
Red Hat Fuse 7.5.0camelFixed 2019-11-14RHSA-2019:3892
Red Hat JBoss Fuse 6camelNot affected
Red Hat Storage 3rhs-hadoopNot affected

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-2018-8009.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

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

References

Check your stackJSON