How severe is GHSA-q6rq-4whr-r879?

GHSA-q6rq-4whr-r879 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-q6rq-4whr-r879?

GHSA-q6rq-4whr-r879 affects the following packages: org.jenkins-ci.plugins:active-directory (Maven). Ecosystems affected: Maven.

How do I fix GHSA-q6rq-4whr-r879?

Update org.jenkins-ci.plugins:active-directory to 2.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q6rq-4whr-r879 is resolved across your whole dependency graph.

How do I detect GHSA-q6rq-4whr-r879 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:active-directory. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-q6rq-4whr-r879 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-q6rq-4whr-r879?

O3 pinpoints whether GHSA-q6rq-4whr-r879 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-q6rq-4whr-r879 actively exploited in the wild?

No public exploit code has been indexed for GHSA-q6rq-4whr-r879 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-q6rq-4whr-r879?

GHSA-q6rq-4whr-r879 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 47th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-q6rq-4whr-r879?

GHSA-q6rq-4whr-r879 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q6rq-4whr-r879 published, and has it been updated?

GHSA-q6rq-4whr-r879 was published on May 24, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-q6rq-4whr-r879

MEDIUM

Missing permission check in Jenkins Active Directory Plugin allows accessing domain health check page

Also known asCVE-2020-2302

Published

May 24, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk47th percentile+0.64%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

☕org.jenkins-ci.plugins:active-directory

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Jenkins Active Directory Plugin 2.19 and earlier does not perform a permission check in an HTTP endpoint.

This allows attackers with Overall/Read permission to access the domain health check diagnostic page.

Jenkins Active Directory Plugin 2.20 requires Overall/Administer permission to access the domain health check diagnostic page.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:active-directory`	all versions	2.20

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:active-directory. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.jenkins-ci.plugins:active-directory to 2.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q6rq-4whr-r879 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-q6rq-4whr-r879 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-q6rq-4whr-r879. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Jenkins Active Directory Plugin 2.19 and earlier does not perform a permission check in an HTTP endpoint. This allows attackers with Overall/Read permission to access the domain health check diagnostic page. Jenkins Active Directory Plugin 2.20 requires Overall/Administer permission to access the domain health check diagnostic page.

O3 Security · Impact-Aware SCA

Is GHSA-q6rq-4whr-r879 in your dependencies?

O3 detects GHSA-q6rq-4whr-r879 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works