CVE-2023-41937 json
SSRF vulnerability in Jenkins Bitbucket Push and Pull Request Plugin allows capturing credentials
published 3y ago modified 4mo ago also GHSA-vrpg-c7c4-8mpx , EUVD-2023-2605
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven io.jenkins.plugins:bitbucket-push-and-pull-request 2.8.4
Is CVE-2023-41937 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-15).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | io.jenkins.plugins:bitbucket-push-and-pull-request | >=2.4.0, <2.8.4 |
2.8.4 |
Affected products
- Jenkins Project Jenkins Bitbucket Push and Pull Request Plugin
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
jenkins.io
/security/advisory/2023-09-06/#SECURITY-3165
vendor-advisory, web
-
openwall.com
/lists/oss-security/2023/09/06/9
web, mailing-list, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-41937
advisory
Sources
- CVE List CVE-2023-41937
- GitHub Advisory GHSA-vrpg-c7c4-8mpx
- NVD CVE-2023-41937
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.