Active DirectoryApplication · Jenkins
CVE-2020-2301
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 Active Directory Plugin 2.19 and earlier allows attackers to log in as any user with any password while a successful authentication of that user is still in the optional cache when using Windows/ADSI mode.
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 Active Directory Plugin versions 2.19 and earlier contains an authentication bypass vulnerability when using Windows/ADSI mode. An attacker can log in as any user with any password while a successful authentication of that user remains in the optional credential cache, effectively bypassing all authentication checks.
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.19CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 Active Directory plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed and look for 'Active Directory' in the list, or check the file META-INF/MANIFEST.MF inside JENKINS_HOME/plugins/active-directory.jpiAffected if The plugin version listed is 2.19 or earlier
-
Confirm ADSI mode is in useIn Jenkins, go to Manage Jenkins > Configure System > Active Directory and locate the domain configuration section. Look for a setting labeled 'ADSI' or 'Windows/ADSI mode' or a checkbox/combo that enables Windows-based ADSI authenticationAffected if Windows/ADSI mode is enabled in the Active Directory domain configuration
-
Verify credential caching is enabledIn the same Active Directory plugin configuration area, look for settings related to caching such as 'Cache', 'Credential Cache', 'Cache Duration', or similar options that control whether successful authentications are storedAffected if Credential caching is turned on (a cache duration or cache-enabled checkbox is present and active)
-
Cross-reference installed version against affected rangeCompare your confirmed plugin version from step 1 against the affected range: any version less than or equal to 2.19Affected if Your installed version is 2.19 or lower AND steps 2 and 3 both confirm ADSI mode with credential caching are in use
You are affected if the Active Directory plugin version is 2.19 or earlier, Windows/ADSI mode is enabled, and credential caching is active - the combination of these three conditions creates the authentication bypass vulnerability.
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.
dbcve · scopedUpdate the Jenkins Active Directory Plugin to a version newer than 2.19. Prior to updating, document the current AD integration configuration and test the upgrade in a non-production environment to ensure authentication continues to function correctly.
Active Directory plugin 2.20 or later
- Check current Jenkins Active Directory plugin version in Manage Jenkins > Manage Plugins > Installed
- Backup Jenkins configuration and user data
- Navigate to Manage Jenkins > Manage Plugins > Available
- Update the Active Directory plugin to version 2.20 or later
- Restart Jenkins to apply the plugin update
- Verify the update was successful and test authentication
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Active Directory
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2301 — 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-2020-2301 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