CVE-2020-2300 json
Improper Authentication (empty password) in Jenkins Active Directory Plugin
published 2020-11-04 6 y ago modified 2026-06-17 4 mo ago also GHSA-8wcw-cw2f-h4g2 , EUVD-2022-3251
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
Jenkins 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.
Patch / fix
- maven org.jenkins-ci.plugins:active-directory 2.16.1, 2.20
- Jenkins project Jenkins Active Directory Plugin 2.16.1
Exploit prediction
1.67% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:active-directory | >=2.17, <2.20 <2.16.1 |
2.20 2.16.1 |
Affected products
- Jenkins project Jenkins Active Directory Plugin
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/jenkinsci/active-directory-plugin/commit/57e78ea7bb96b4e59405f28959ade2d26821163d
web
-
jenkins.io
/security/advisory/2020-11-04/#SECURITY-2099
web, vendor-advisory
-
openwall.com
/lists/oss-security/2020/11/04/6
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-2300
advisory
-
github.com
/CVEProject/cvelist/blob/381fe967666a5ce01625a7a050427aa4757e3ca6/2020/2xxx/CVE-2020-2300.json
web
-
github.com
/jenkinsci/active-directory-plugin
package
Sources
- CVE List CVE-2020-2300
- GitHub Advisory GHSA-8wcw-cw2f-h4g2
- NVD CVE-2020-2300
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.