CVE-2020-2235 json
CSRF vulnerability in Jenkins Pipeline Maven Integration Plugin allow capturing credentials
published 6y ago modified 4mo ago also GHSA-c2hg-2jj6-h8vh , EUVD-2022-3476
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
A cross-site request forgery (CSRF) vulnerability in Jenkins Pipeline Maven Integration Plugin 3.8.2 and earlier allows attackers to connect to an attacker-specified JDBC URL using attacker-specified credentials IDs obtained through another method, potentially capturing credentials stored in Jenkins.
Patch / fix
- maven org.jenkins-ci.plugins:pipeline-maven 3.8.3
Is CVE-2020-2235 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 FencerExploit prediction
0.86% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 7.1 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:pipeline-maven | <3.8.3 |
3.8.3 |
Affected products
- Jenkins project Jenkins Pipeline Maven Integration Plugin
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
- jenkins.io /security/advisory/2020-08-12/#SECURITY-1794%20%282%29
-
openwall.com
/lists/oss-security/2020/08/12/4
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-2235
advisory
-
github.com
/jenkinsci/pipeline-maven-plugin
web
-
jenkins.io
/security/advisory/2020-08-12/#SECURITY-1794%20(2)
web
Sources
- CVE List CVE-2020-2235
- GitHub Advisory GHSA-c2hg-2jj6-h8vh
- NVD CVE-2020-2235
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.