Active DirectoryApplication · Jenkins
CVE-2017-2649
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 · uneditedIt was found that the Active Directory Plugin for Jenkins up to and including version 2.2 did not verify certificates of the Active Directory server, thereby enabling 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 Active Directory Plugin for Jenkins versions 2.2 and earlier fails to validate SSL/TLS certificates when establishing connections to Active Directory servers, allowing man-in-the-middle attackers to intercept and manipulate authentication traffic between Jenkins and AD.
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
Active DirectoryApplication
<= 2.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/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 if Active Directory plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or use: java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins. Alternatively, inspect $JENKINS_HOME/plugins/ for active-directory.jpi or active-directory-plugin.jpiAffected if plugin is not present in the list or plugins directory
-
Determine installed Active Directory plugin versionIn Manage Jenkins > Manage Plugins > Installed, locate the Active Directory entry and note the Version column. Or extract from manifest: unzip -p $JENKINS_HOME/plugins/active-directory.jpi META-INF/MANIFEST.MFAffected if version displays as 2.2 or earlier (e.g., 2.2, 2.1, 2.0, 1.x)
-
Confirm Active Directory is configured as security realmGo to Manage Jenkins > Configure Global Security > Access Control (or Security Realm). Check if Active Directory is selected and domain controller settings are specified.Affected if Active Directory is selected as the security realm with domain credentials configured
You are affected if the Active Directory plugin version is 2.2 or earlier AND Active Directory is actively configured as the security realm in Jenkins.
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 dataUpdate the Active Directory Plugin to version 2.3 or later which implements proper certificate verification for Active Directory connections.
Fix this in Active Directory
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2649 — 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-2649 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