Missing permission check in Jenkins RocketChat Notifier PluginGHSA-4p8f-2fwv-6xcw
MEDIUMFix: jenkinsci/rocketchatnotifier-plugin@1a0023bGHSA-4p8f-2fwv-6xcw is a medium-severity (CVSS 4.3) CWE-862 vulnerability in org.jenkins-ci.plugins:rocketchatnotifier. A fix is available for org.jenkins-ci.plugins:rocketchatnotifier — see the affected versions and patch details below.
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:rocketchatnotifierReal-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 RocketChat Notifier Plugin 1.4.10 and earlier does not perform a permission check in a method implementing form validation.
This allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials.
Additionally, this form validation method does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
RocketChat Notifier Plugin 1.5.0 requires POST requests and Overall/Administer permission for the affected form validation method.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:rocketchatnotifier | all versions | 1.5.0org.jenkins-ci.plugins:rocketchatnotifier:1.5.0 |
Affected Products
rocketchat notifierjenkinsDetection & 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:rocketchatnotifier, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:rocketchatnotifier to 1.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4p8f-2fwv-6xcw is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-4p8f-2fwv-6xcw in your dependencies?
Find it across Maven, including transitive dependencies.