Active DirectoryApplication · Jenkins
CVE-2020-2300
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 does not prohibit the use of an empty password in Windows/ADSI mode, which allows attackers to log in to Jenkins as any user depending on the configuration of the Active Directory server.
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 fails to validate or prohibit empty passwords when operating in Windows/ADSI mode. If the Active Directory server is configured to accept empty passwords (which is a weak configuration but does occur in some environments), an attacker can authenticate as any user in the domain without knowing their password.
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.
-
Verify Active Directory plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and look for 'Active Directory' plugin, or check for the presence of active-directory.jpi or active-directory.hpi in the Jenkins plugins directoryAffected if The Active Directory plugin is not installed or not in use, then this CVE does not apply
-
Check installed plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed, find the Active Directory plugin and note the version number displayedAffected if The installed version is 2.19 or earlier (e.g., 2.19, 2.18, 2.17, etc.)
-
Confirm ADSI mode is configuredGo to Manage Jenkins > Configure Global Security and locate the Active Directory domain configuration section. Check if 'Windows' mode or 'ADSI' mode is selected for the domain bindingAffected if The plugin is configured to use Windows/ADSI mode; if it uses only 'LDAP' or 'JNDI' mode, this specific vulnerability does not apply
You are affected if you have the Active Directory plugin installed at version 2.19 or earlier AND it is configured to use Windows/ADSI mode (the vulnerability only applies in that specific mode).
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 Active Directory Plugin to version 2.20 or later, which enforces password validation and prohibits empty passwords. Also review and harden Active Directory server configuration to reject empty passwords.
Fix this in Active Directory
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2300 — 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-2300 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