dbcve.org
MavenApplication · Jenkins

CVE-2017-1000397

MEDIUM · 5.9 CVSS v3.0 Published 2018-01-26
Fix available
A fix is available. Upgrade to after 2.17 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Jenkins Maven Plugin 2.17 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. Maven Plugin 3.0 no longer has a dependency on commons-httpclient.

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

Jenkins Maven Plugin versions 2.17 and earlier bundled a vulnerable version of commons-httpclient (CVE-2012-6153) that incorrectly verified SSL certificates, allowing man-in-the-middle attackers to intercept communications by impersonating legitimate servers through invalid certificates.

MitigationUpgrade Jenkins Maven Plugin to version 3.0 or later, which removes the vulnerable commons-httpclient dependency entirely.

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
MavenApplication
Affected:<= 2.17

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
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 checks

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

  1. Check if Jenkins Maven Plugin is installed
    Locate the Jenkins Maven Plugin in your Jenkins installation by checking the plugin management console or the plugins directory
    Affected if Plugin is present in the Jenkins environment
  2. Identify the installed version of Jenkins Maven Plugin
    Use the Jenkins plugin manager or CLI to query the version of the Jenkins Maven Plugin (also known as maven-plugin)
    Affected if Version is 2.17 or earlier
  3. Verify the commons-httpclient library is bundled
    Inspect the Jenkins Maven Plugin WAR file or plugin directory for the presence of commons-httpclient library
    Affected if commons-httpclient JAR file exists within the maven plugin directory
  4. Check SSL-enabled configurations
    Review Jenkins job configurations that use Maven builds with HTTPS/SSL-enabled repository URLs
    Affected if Maven builds connect to HTTPS repositories using the vulnerable plugin version

You are affected if Jenkins Maven Plugin version 2.17 or earlier is installed and Maven builds connect to HTTPS repositories through the plugin.

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
Upgrade available Upgrade to a release after 2.17
Interim mitigation

Upgrade Jenkins Maven Plugin to version 3.0 or later, which removes the vulnerable commons-httpclient dependency entirely.

Fix this in Maven Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000397 — 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-2017-1000397 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