HadoopApplication · Apache
CVE-2017-3162
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 · uneditedHDFS 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.
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 confidenceApache Hadoop before 2.7.0 contains an input validation vulnerability in the HDFS DataNode servlet used for namespace browsing. The NameNode query parameter is not validated, allowing an attacker to make the DataNode connect to arbitrary servers (Server-Side Request Forgery). This could enable internal network reconnaissance or attacks against other services.
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
<= 2.6.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Hadoop versionRun 'hadoop version' or check the Hadoop jars and documentation to determine the exact version numberAffected if Version is 2.6.5 or earlier (any version <= 2.6.5)
-
Verify DataNode web UI is enabledCheck Hadoop configuration files (hdfs-site.xml) for dfs.datanode.http.address and confirm the DataNode web interface is configured and accessible on the typical port 50075Affected if DataNode HTTP server is enabled and publicly or semi-publicly accessible on the network
-
Confirm namespace browsing servlet is exposedAccess the DataNode web UI path '/browseDirectory.jsp' or similar namespace browsing endpoints and verify the servlet respondsAffected if The DataNode servlet used for namespace browsing is accessible without additional authentication barriers
-
Test NameNode parameter injectionSubmit an HTTP request to the DataNode servlet with a manipulated 'namenode' query parameter pointing to an external or internal IP address (for detection purposes, use a controlled test endpoint)Affected if The servlet accepts arbitrary NameNode hostnames or IP addresses in the parameter without validation
You are affected if you run Hadoop version 2.6.5 or earlier AND the DataNode servlet for namespace browsing is accessible on the network with the NameNode query parameter accepting unvalidated values.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Apache Hadoop to version 2.7.0 or later, or implement strict validation of the NameNode query parameter in the DataNode servlet to ensure only legitimate NameNode addresses are accepted.
Fix this in Hadoop
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3162 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-3162 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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