CVE-2019-1003043: High severity jenkins slack notification vulnerability
A missing permission check in Jenkins Slack Notification Plugin 2.19 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.
Other sources
Jenkins Slack Notification Plugin did not perform permission checks on a method implementing form validation. This allowed users with Overall/Read access to Jenkins to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Additionally, this form validation method did not require POST requests, resulting in a cross-site request forgery vulnerability.
This form validation method now requires POST requests and Overall/Administer (for global configuration) or Item/Configure permissions (for job configuration).
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2019-1003043?
CVE-2019-1003043 is classified as a critical vulnerability due to its potential to expose sensitive credentials in Jenkins.
How do I fix CVE-2019-1003043?
To fix CVE-2019-1003043, update the Jenkins Slack Notification Plugin to version 2.20 or later.
What versions are affected by CVE-2019-1003043?
CVE-2019-1003043 affects Jenkins Slack Notification Plugin versions up to and including 2.19.
What type of attack does CVE-2019-1003043 enable?
CVE-2019-1003043 allows attackers with Overall/Read permission to connect to attacker-specified URLs and capture Jenkins credentials.
Who is impacted by CVE-2019-1003043?
Any Jenkins user with Overall/Read permission could be impacted by CVE-2019-1003043 if they have access to the vulnerable Slack Notification Plugin.