HadoopApplication · Apache
CVE-2017-7669
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 · uneditedIn Apache Hadoop 2.8.0, 3.0.0-alpha1, and 3.0.0-alpha2, the LinuxContainerExecutor runs docker commands as root with insufficient input validation. When the docker feature is enabled, authenticated users can run commands as root.
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 confidenceIn Apache Hadoop 2.8.0 through 3.0.0-alpha2, the LinuxContainerExecutor executes Docker commands as root without adequate input validation. When the Docker feature is enabled, authenticated users can exploit insufficient sanitization of Docker command parameters to execute arbitrary commands with root privileges on the host system.
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.8.0= 3.0.0CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Hadoop versionRun 'hadoop version' or check the Hadoop installation directory to determine the exact version numberAffected if The version is 2.8.0 or 3.0.0 (including 3.0.0-alpha1 or 3.0.0-alpha2)
-
Verify LinuxContainerExecutor is in useCheck yarn-site.xml for the property 'yarn.nodemanager.container-executor.class' and confirm it references LinuxContainerExecutorAffected if The LinuxContainerExecutor class is configured and in use
-
Confirm Docker feature is enabledCheck container-executor.cfg or yarn-site.xml for Docker-related configuration properties such as 'yarn.nodemanager.docker-container-executor.enabled' or similar Docker enable flagsAffected if Docker execution is explicitly enabled in the Hadoop container executor configuration
-
Review container executor binary permissionsInspect the permissions and ownership of the container-executor binary in the Hadoop bin directory - it should be owned by root with specific setuid bitsAffected if The container-executor binary has elevated permissions allowing root-level command execution
A user is affected if they run a vulnerable Hadoop version (2.8.0 through 3.0.0-alpha2) with LinuxContainerExecutor enabled and the Docker feature turned on in their configuration.
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 dataApply vendor patches for CVE-2017-7669 which add proper input validation to the LinuxContainerExecutor to prevent command injection. Until patched, consider disabling the Docker feature in Hadoop if not required, or implement additional access controls on the Hadoop cluster.
Fix this in Hadoop
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7669 — 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-7669 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