CVE-2022-41245 json
CSRF vulnerability in Jenkins Worksoft Execution Manager Plugin allows capturing credentials
published 4y ago modified 4mo ago also GHSA-ghq7-85hp-fh76 , EUVD-2022-6823
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
A cross-site request forgery (CSRF) vulnerability in Jenkins Worksoft Execution Manager Plugin 10.0.3.503 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Is CVE-2022-41245 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
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:ws-execution-manager | all versions |
no fix listed |
Affected products
- Jenkins project Jenkins Worksoft Execution Manager Plugin
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
jenkins.io
/security/advisory/2022-09-21/#SECURITY-2237
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-41245
advisory
-
github.com
/jenkinsci/ws-execution-manager-plugin
package
Sources
- CVE List CVE-2022-41245
- GitHub Advisory GHSA-ghq7-85hp-fh76
- NVD CVE-2022-41245
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.