JenkinsApplication
CVE-2017-1000396
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 2.73.1 and earlier, 2.83 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. This library is widely used as a transitive dependency in Jenkins plugins. The fix for CVE-2012-6153 was backported to the version of commons-httpclient that is bundled in core and made available to plugins.
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 confidenceJenkins bundled a version of commons-httpclient containing CVE-2012-6153, which incorrectly verifies SSL certificates, enabling man-in-the-middle attacks. This library is widely used as a transitive dependency across Jenkins plugins, extending the attack surface beyond core functionality.
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
JenkinsApplication
<= 2.73.1<= 2.83CVSS 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 the installed Jenkins versionNavigate to Manage Jenkins > About Jenkins in the web UI, or run: java -jar jenkins.war --version (if running from war), or check the Jenkins service/package version on the hostAffected if The version displayed is 2.73.1 or earlier, or 2.83 or earlier (note: 2.74-2.83 range may also be affected depending on the exact bundle)
-
Locate the bundled commons-httpclient libraryCheck the jenkins.war contents (jar tf jenkins.war | grep commons-httpclient) or find it in the JENKINS_HOME/war directory; the jar file name typically contains the version numberAffected if The commons-httpclient jar version is 3.1 or earlier, which contains the SSL verification flaw from CVE-2012-6153
-
Determine if outbound HTTPS connections are in useReview Jenkins system configuration (Manage Jenkins > Configure System) for HTTP/HTTPS endpoints configured in plugins, build steps, or remote API calls; also check plugin configurations for any HTTP client usageAffected if Any plugin or configuration makes outbound HTTPS requests to external services, which would rely on the flawed certificate verification
You are affected if your Jenkins version is 2.73.1 or earlier, or 2.83 or earlier, AND the system or its plugins make outbound HTTPS connections, as the bundled commons-httpclient library incorrectly verifies SSL certificates.
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 Jenkins to version 2.73.2 or later (or 2.84+) to receive the backported fix for CVE-2012-6153 in the bundled commons-httpclient library.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000396 — 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-1000396 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