Jenkins Sonar Gerrit Plugin vulnerable to Cross-Site Request ForgeryGHSA-m82g-fv7v-h64m
MEDIUMFix: jenkinsci/sonar-gerrit-plugin@f4646d4GHSA-m82g-fv7v-h64m is a medium-severity (CVSS 5.4) Cross-Site Request Forgery (CSRF) vulnerability in org.jenkins-ci.plugins:sonar-gerrit. A fix is available for org.jenkins-ci.plugins:sonar-gerrit — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-m82g-fv7v-h64m.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.jenkins-ci.plugins:sonar-gerritReal-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
A cross-site request forgery (CSRF) vulnerability in Jenkins Sonar Gerrit Plugin 377.v8f3808963dc5 and earlier allows attackers to have Jenkins connect to Gerrit servers (previously configured by Jenkins administrators) using attacker-specified credentials IDs obtained through another method, potentially capturing credentials stored in Jenkins.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:sonar-gerrit | all versions | 378.vf4646d4df087org.jenkins-ci.plugins:sonar-gerrit:378.vf4646d4df087 |
Affected Products
sonar gerritjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:sonar-gerrit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:sonar-gerrit to 378.vf4646d4df087 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m82g-fv7v-h64m 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.
Frequently Asked Questions
Is GHSA-m82g-fv7v-h64m in your dependencies?
Find it across Maven, including transitive dependencies.