CVE-2023-41937 — bitbucket-push-and-pull-r…
HIGHCVE-2023-41937 is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in io.jenkins.plugins:bitbucket-push-and-pull-request. A fix is available for io.jenkins.plugins:bitbucket-push-and-pull-request — see the affected versions and patch details below.
SSRF vulnerability in Jenkins Bitbucket Push and Pull Request Plugin allows capturing credentials
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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 CVE-2023-41937.
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
io.jenkins.plugins:bitbucket-push-and-pull-requestReal-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 Bitbucket Push and Pull Request Plugin 2.4.0 through 2.8.3 (both inclusive) trusts values provided in the webhook payload, including certain URLs, and uses configured Bitbucket credentials to connect to those URLs, allowing attackers to capture Bitbucket credentials stored in Jenkins by sending a crafted webhook payload.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.jenkins.plugins:bitbucket-push-and-pull-request | ≥ 2.4.0&&< 2.8.4 | 2.8.4io.jenkins.plugins:bitbucket-push-and-pull-request:2.8.4 |
Affected Products
bitbucket push and pull requestjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:bitbucket-push-and-pull-request, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:bitbucket-push-and-pull-request to 2.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-41937 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2023-41937 in your dependencies?
Find it across Maven, including transitive dependencies.