# CVE-2020-2302: Missing permission check in Jenkins Active Directory Plugin allows accessing domain health check page

> Attackers with read permissions can access sensitive domain health check diagnostics due to missing authorization checks in the Jenkins Active Directory Plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q6rq-4whr-r879

## What is CVE-2020-2302?

CVE-2020-2302 is a medium-severity missing authorization vulnerability in Jenkins Active Directory Plugin, published on 4 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A missing permission check in Jenkins Active Directory Plugin 2.19 and earlier allows attackers with Overall/Read permission to access the domain health check diagnostic page.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2020-2302?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:active-directory. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:active-directory` | Maven | All versions | 2.20 |
| `org.jenkins-ci.plugins:active-directory` | Maven | All versions | 2.20 |

Products: Jenkins Active Directory.

## How do I fix CVE-2020-2302?

Upgrade org.jenkins-ci.plugins:active-directory to 2.20 or later.

## Is CVE-2020-2302 being exploited?

There is no known exploitation of CVE-2020-2302 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Active Directory Plugin

- [CVE-2020-2299](https://insights.sbomify.com/CVE-2020-2299/): Improper Authentication in Jenkins Active Directory Plugin (critical 9.8)
- [CVE-2020-2300](https://insights.sbomify.com/CVE-2020-2300/): Improper Authentication (empty password) in Jenkins Active Directory Plugin (critical 9.8)
- [CVE-2020-2301](https://insights.sbomify.com/CVE-2020-2301/): Authentication cache in Active Directory Jenkins Plugin allows logging in with any password (critical 9.8)
- [CVE-2017-2649](https://insights.sbomify.com/CVE-2017-2649/): Jenkins Active Directory Plugin did not verify certificate of AD server (high 8.1)
- [CVE-2019-1003009](https://insights.sbomify.com/CVE-2019-1003009/): Jenkins Active Directory Plugin Improper certificate validation with StartTLS (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-2302 and fix it if it is affected.

What it is: CVE-2020-2302 is a medium-severity missing authorization vulnerability in Jenkins Active Directory Plugin, published on 4 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-2302 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:active-directory (Maven): affected all versions; fixed in 2.20
- org.jenkins-ci.plugins:active-directory (Maven): affected all versions; fixed in 2.20

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-2302/ (Markdown: https://insights.sbomify.com/CVE-2020-2302/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-2302
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-2302
- OSV: https://osv.dev/vulnerability/CVE-2020-2302

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-2302/
Summaries are generated and may contain mistakes; the official description above is the record.