dbcve.org
HadoopApplication · Apache

CVE-2014-0229

MEDIUM · 6.5 CVSS v3.0 Published 2017-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Apache Hadoop 0.23.x before 0.23.11 and 2.x before 2.4.1, as used in Cloudera CDH 5.0.x before 5.0.2, do not check authorization for the (1) refreshNamenodes, (2) deleteBlockPool, and (3) shutdownDatanode HDFS admin commands, which allows remote authenticated users to cause a denial of service (DataNodes shutdown) or perform unnecessary operations by issuing a command.

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 confidence

Three HDFS admin commands (refreshNamenodes, deleteBlockPool, shutdownDatanode) in Apache Hadoop 0.23.x before 0.23.11 and 2.x before 2.4.1 bypass authorization checks, allowing any authenticated user to trigger DataNode shutdown or unnecessary operations.

MitigationUpgrade to Hadoop 0.23.11+, 2.4.1+, or CDH 5.0.2+ to include the authorization checks for these admin commands.

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
Affected:= 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= 2.0.0= 2.0.1
CdhApplication
Affected:= 5.0.0

CVSS 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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Hadoop version
    Run 'hadoop version' to display the installed Hadoop version number
    Affected if Version is 0.23.x before 0.23.11, or 2.x before 2.4.1, or CDH 5.0.0 (exact versions: 0.23.0-0.23.10, 2.0.0-2.0.1, 2.1.0-2.4.0)
  2. Confirm HDFS is the filesystem in use
    Check core-site.xml for 'fs.defaultFS' property or run 'hdfs getconf -confKey fs.defaultFS' to see if HDFS is configured
    Affected if fs.defaultFS points to hdfs:// (HDFS is active)
  3. Verify the three vulnerable admin commands exist
    Run 'hdfs dfsadmin -help refreshNamenodes', 'hdfs dfsadmin -help deleteBlockPool', and 'hdfs dfsadmin -help shutdownDatanode' to confirm these commands are available
    Affected if All three commands are available and respond to -help without authorization errors

You are affected if your Hadoop version falls within the vulnerable ranges AND HDFS is your active filesystem, allowing any authenticated user to execute these admin commands without proper authorization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Hadoop 0.23.11+, 2.4.1+, or CDH 5.0.2+ to include the authorization checks for these admin commands.

Fix this in Hadoop Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0229 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0229 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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