How severe is CVE-2020-2299?

CVE-2020-2299 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2020-2299 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (68th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-2299?

CVE-2020-2299 affects Jenkins Active Directory. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-2299?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2020-2299 published?

CVE-2020-2299 was published on 2020-11-04 and last updated on 2026-06-17.

CVE-2020-2299

CVE-2020-2299 is a critical-severity vulnerability in Jenkins Active Directory with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 1% (68th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Jenkins Active Directory
Published: 2020-11-04
Last modified: 2026-06-17

Description

Jenkins Active Directory Plugin 2.19 and earlier allows attackers to log in as any user if a magic constant is used as the password.

Frequently asked questions

What is CVE-2020-2299?: Jenkins Active Directory Plugin 2.19 and earlier allows attackers to log in as any user if a magic constant is used as the password.
How severe is CVE-2020-2299?: CVE-2020-2299 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-2299 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (68th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-2299?: CVE-2020-2299 affects Jenkins Active Directory. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-2299?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2020-2299 published?: CVE-2020-2299 was published on 2020-11-04 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:jenkins:active_directory:*:*:*:*:*:jenkins:*:*

More vulnerabilities in Jenkins Active Directory

CVE-2020-2301 — Critical (CVSS 9.8): Jenkins Active Directory Plugin 2.19 and earlier allows attackers to log in as any user with any password while a…
CVE-2020-2300 — Critical (CVSS 9.8): Jenkins Active Directory Plugin 2.19 and earlier does not prohibit the use of an empty password in Windows/ADSI mode,…
CVE-2017-2649 — High (CVSS 8.1): It was found that the Active Directory Plugin for Jenkins up to and including version 2.2 did not verify certificates…
CVE-2019-1003009 — High (CVSS 7.4): An improper certificate validation vulnerability exists in Jenkins Active Directory Plugin 2.10 and earlier in…
CVE-2026-48919 — Medium (CVSS 6.6): Jenkins Active Directory Plugin 2.41 and earlier deserializes data from LDAP referrals without validation.
CVE-2026-48918 — Medium (CVSS 6.6): Jenkins Active Directory Plugin 2.41 and earlier follows LDAP referrals by default.

All CVEs affecting Jenkins Active Directory →