CVE-2015-7539: High severity jenkins lts vulnerability
The Plugins Manager in Jenkins before 1.640 and LTS before 1.625.2 does not verify checksums for plugin files referenced in update site data, which makes it easier for man-in-the-middle attackers to execute arbitrary code via a crafted plugin.
Other sources
While the Jenkins update site data is digitally signed, and the signature verified by Jenkins, Jenkins did not verify the provided SHA-1 checksums for the plugin files referenced in the update site data. This enabled MITM attacks on the plugin manager, resulting in installation of attacker-provided plugins.
This could allow attackers able to manipulate the network path between Jenkins and the update site to install and run arbitrary code on Jenkins.
External References:
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2015-7539?
CVE-2015-7539 is considered a critical vulnerability due to its potential for arbitrary code execution.
How do I fix CVE-2015-7539?
To fix CVE-2015-7539, upgrade Jenkins to version 1.641 or 1.625.3 for LTS.
Which versions of Jenkins are affected by CVE-2015-7539?
Versions of Jenkins prior to 1.640 and LTS versions before 1.625.2 are affected by CVE-2015-7539.
What are the potential risks of CVE-2015-7539?
CVE-2015-7539 allows man-in-the-middle attackers to execute arbitrary code, posing significant security risks.
Is CVE-2015-7539 specific to certain environments?
CVE-2015-7539 affects Jenkins installations across various environments, including those using Red Hat OpenShift.