CVE-2015-5320: Infoleak
Jenkins before 1.638 and LTS before 1.625.2 do not properly verify the shared secret used in JNLP slave connections, which allows remote attackers to connect as slaves and obtain sensitive information or possibly gain administrative access by leveraging knowledge of the name of a slave.
Other sources
The following flaw was found in Jenkins:
JNLP slave connections did not verify that the correct secret was supplied, which allowed malicious users to connect their own machines as slaves to Jenkins knowing only the name of the slave. This enables attackers to take over Jenkins (unless the slave-to-master security subsystem is enabled) or gain access to private data like keys and source code.
This issue allowos for several different attacks, compromising integrity, stability and confidentiality.
External References:
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2015-5320?
CVE-2015-5320 is classified as a critical vulnerability due to its potential to allow unauthorized remote access and administrative privileges.
How do I fix CVE-2015-5320?
To mitigate CVE-2015-5320, upgrade Jenkins to version 1.638 or later, or LTS to version 1.625.2 or later.
What versions of Jenkins are affected by CVE-2015-5320?
Jenkins versions prior to 1.638 and LTS versions prior to 1.625.2 are affected by CVE-2015-5320.
Can CVE-2015-5320 allow attackers to compromise sensitive data?
Yes, CVE-2015-5320 could allow remote attackers to connect as slaves and gain access to sensitive information.
Is CVE-2015-5320 specific only to Jenkins?
CVE-2015-5320 primarily affects Jenkins, but it may also impact OpenShift versions that include Jenkins versions prior to the fixed releases.