CVE-2020-2117: High severity Jenkins Pipeline Github Notify Step Jenkins vulnerability
A missing permission check in Jenkins Pipeline GitHub Notify Step Plugin 1.0.4 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/org.jenkins-ci.plugins:pipeline-githubnotify-stepto a version that resolves this vulnerability.Fixed in 1.0.5
Event History
Frequently Asked Questions
What is the severity of CVE-2020-2117?
CVE-2020-2117 has been rated as a Medium severity vulnerability.
How do I fix CVE-2020-2117?
To fix CVE-2020-2117, upgrade Jenkins Pipeline GitHub Notify Step Plugin to version 1.0.5 or later.
Who is affected by CVE-2020-2117?
CVE-2020-2117 affects users of Jenkins Pipeline GitHub Notify Step Plugin versions 1.0.4 and earlier.
What type of attack does CVE-2020-2117 enable?
CVE-2020-2117 enables attackers to connect to arbitrary URLs and capture credentials stored in Jenkins.
What privileges are required to exploit CVE-2020-2117?
An attacker needs Overall/Read permission in Jenkins to exploit CVE-2020-2117.