CVE-2020-2116 json
CSRF vulnerability in Pipeline GitHub Notify Step Plugin allows capturing credentials
published 6y ago modified 4mo ago also GHSA-qhxf-m7jm-jc57 , EUVD-2022-4980
- cvss
- 8.8
- 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
A cross-site request forgery vulnerability in Jenkins Pipeline GitHub Notify Step Plugin 1.0.4 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.
Patch / fix
- maven org.jenkins-ci.plugins:pipeline-githubnotify-step 1.0.5
Is CVE-2020-2116 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.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 7.1 | CVSS:3.1/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-githubnotify-step | <1.0.5 |
1.0.5 |
Affected products
- Jenkins project Jenkins Pipeline GitHub Notify Step Plugin
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
- jenkins.io /security/advisory/2020-02-12/#SECURITY-812%20%281%29
-
openwall.com
/lists/oss-security/2020/02/12/3
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-2116
advisory
-
github.com
/jenkinsci/pipeline-githubnotify-step-plugin
package
-
jenkins.io
/security/advisory/2020-02-12/#SECURITY-812%20(1)
web
Sources
- CVE List CVE-2020-2116
- GitHub Advisory GHSA-qhxf-m7jm-jc57
- NVD CVE-2020-2116
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.