SwarmApplication · Jenkins
CVE-2017-1000402
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 · uneditedJenkins Swarm Plugin Client 3.4 and earlier bundled a version of the commons-httpclient library with the vulnerability CVE-2012-6153 that incorrectly verified SSL certificates, making it susceptible to man-in-the-middle attacks.
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 confidenceThe Jenkins Swarm Plugin Client 3.4 and earlier bundled a vulnerable version of commons-httpclient (CVE-2012-6153) that incorrectly verified SSL certificates. This flaw allows man-in-the-middle attackers to intercept encrypted communications by presenting fraudulent SSL certificates that the library would incorrectly accept as valid.
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
SwarmApplication
<= 3.4CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
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 Jenkins Swarm Plugin Client versionLocate the swarm-client JAR file (typically swarm-client-*.jar in the Jenkins plugins or tools directory) and check its filename version, or run: java -jar swarm-client-[filename].jar --version 2>/dev/null, or inspect the manifest.mf file inside the JAR for the Implementation-Version attributeAffected if The version is 3.4 or lower (e.g., 3.4, 3.3, 3.2, etc.)
-
Verify plugin is actively usedCheck if the swarm client is configured to connect to a Jenkins master by reviewing the startup arguments or configuration files (e.g., -master, -username, or similar Swarm client parameters)Affected if The swarm client is actively connecting to a Jenkins master over HTTPS
-
Confirm SSL/TLS communication is enabledReview the connection configuration to determine if HTTPS is being used for master-slave communication (look for -https URLs or SSL-enabled endpoints in the swarm client configuration)Affected if HTTPS communication is configured between the swarm client and Jenkins master
-
Check bundled commons-httpclient versionExtract the commons-httpclient JAR from within the swarm-client JAR (located in the lib or plugins directory of the distribution) and check its version, or inspect the manifest classpath entries inside the swarm-client JARAffected if The bundled commons-httpclient version corresponds to a release prior to the CVE-2012-6153 fix (typically version 3.1 or earlier)
You are affected if you are running Jenkins Swarm Plugin Client version 3.4 or earlier and using it to connect to a Jenkins master over HTTPS or other SSL-protected communications.
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 the Jenkins Swarm Plugin Client to version 3.5 or later, which bundles a fixed version of commons-httpclient with proper SSL certificate verification.
Fix this in Swarm
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000402 — 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-1000402 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