Skip to content

← Public intelligence

Maven package

org.apache.hadoop:hadoop-client

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

5 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratedMavenPublished

    Improper Link Resolution Before File Access in Apache Hadoop

    CVE-2014-3627 · GHSA-jpmf-8cj2-595g

    Affected
    • Maven org.apache.hadoop:hadoop-client >= 0.23.0, < 1.0.1; >= 2.0.0, < 2.5.2
    Fixed in
    2.5.21.0.1· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 2.5.2 or 1.0.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. UnratedMavenPublished

    Client BlockTokens not checked in Apache Hadoop

    CVE-2012-3376 · GHSA-qmh2-h7r6-gm6q

    Affected
    • Maven org.apache.hadoop:hadoop-client >= 2.0.0-alpha, <= 2.0.0-alpha
    Fixed in
    2.0.1-alpha· Vendor fix available
    Issue
    DataNodes in Apache Hadoop 2.0.0 alpha does not check the BlockTokens of clients when Kerberos is enabled and the DataNode has checked out the same BlockPool twice from a NodeName, which might allow remote clients to read arbitrary blocks, write to blocks to which they only have read access, and have other unspecified impacts.

    Recommended action: Upgrade to 2.0.1-alpha (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Critical, CVSS 9.8MavenPublished

    Use of a Broken or Risky Cryptographic Algorithm in Apache Hadoop

    CVE-2012-4449 · GHSA-q46v-cj5v-hvg6

    Affected
    • Maven org.apache.hadoop:hadoop-client < 0.23.4; >= 1.0.0, < 1.0.4; >= 2.0.0, < 2.0.2
    Fixed in
    1.0.42.0.20.23.4· Vendor fix available
    Issue
    Apache Hadoop before 0.23.4, 1.x before 1.0.4, and 2.x before 2.0.2 generate token passwords using a 20-bit secret when Kerberos security features are enabled, which makes it easier for context-dependent attackers to crack secret keys via a brute-force attack.

    Recommended action: Upgrade to 2.0.2, 1.0.4 or 0.23.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  4. Medium, CVSS 6.1MavenPublished

    Improper Neutralization of Input During Web Page Generation in Apache Hadoop

    CVE-2017-3161 · GHSA-qm7f-r83w-3p46

    Affected
    • Maven org.apache.hadoop:hadoop-client <= 2.6.5
    Fixed in
    2.7.0· Vendor fix available
    Issue
    The HDFS web UI in Apache Hadoop before 2.7.0 is vulnerable to a cross-site scripting (XSS) attack through an unescaped query parameter.

    Recommended action: Upgrade to 2.7.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  5. High, CVSS 7.3MavenPublished

    Improper Input Validation in Apache Hadoop

    CVE-2017-3162 · GHSA-pr9x-qmp5-j3rr

    Affected
    • Maven org.apache.hadoop:hadoop-client <= 2.6.5
    Fixed in
    2.7.0· Vendor fix available
    Issue
    HDFS clients interact with a servlet on the DataNode to browse the HDFS namespace. The NameNode is provided as a query parameter that is not validated in Apache Hadoop before 2.7.0.

    Recommended action: Upgrade to 2.7.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →