CVE-2020-2299

Jenkins Active Directory Plugin implements two separate modes: Integration with ADSI on Windows, and an OS agnostic LDAP-based mode.

The LDAP-based mode in Active Directory Plugin starting in version 1.44 and prior to versions 2.16.1 and 2.20 shares code between user lookup and user authentication and distinguishes these behaviors through the use if a magic constant used in place of a real password. This allows attackers to log in as any user if the magic constant is used as the password in Active Directory Plugin prior to 2.16.1 and 220.

Active Directory Plugin 2.16.1 and 2.20 no longer uses a magic constant to distinguish between user lookup and user authentication.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2020-2299 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.20, 2.16.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2020-2299? CVE-2020-2299 is a critical-severity improper authentication vulnerability in org.jenkins-ci.plugins:active-directory (maven), affecting versions >= 2.17, < 2.20. It is fixed in 2.20, 2.16.1. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2020-2299? CVE-2020-2299 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.jenkins-ci.plugins:active-directory are affected by CVE-2020-2299? org.jenkins-ci.plugins:active-directory (maven) versions >= 2.17, < 2.20 is affected.
4. Is there a fix for CVE-2020-2299? Yes. CVE-2020-2299 is fixed in 2.20, 2.16.1. Upgrade to this version or later.
5. Is CVE-2020-2299 exploitable, and should I be worried? Whether CVE-2020-2299 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2020-2299 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2020-2299?
   • Upgrade org.jenkins-ci.plugins:active-directory to 2.20 or later
   • Upgrade org.jenkins-ci.plugins:active-directory to 2.16.1 or later