CVE-2020-2105: Medium severity Jenkins Jenkins vulnerability
Jenkins 2.218 and earlier, LTS 2.204.1 and earlier does not serve the X-Frame-Options: deny HTTP header on REST API responses to protect against clickjacking attacks. An attacker could exploit this by routing the victim through a specially crafted web page that embeds a REST API endpoint in an iframe and tricking the user into performing an action which would allow for the attacker to learn the content of that REST API endpoint.
Jenkins 2.219, LTS 2.204.2 now adds the X-Frame-Options: deny HTTP header to REST API responses, which prevents these types of clickjacking attacks.
Other sources
REST API endpoints in Jenkins 2.218 and earlier, LTS 2.204.1 and earlier were vulnerable to clickjacking attacks.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/org.jenkins-ci.main:jenkins-coreto a version that resolves this vulnerability.Fixed in 2.219 - Upgrade
Upgrade
maven/org.jenkins-ci.main:jenkins-coreto a version that resolves this vulnerability.Fixed in 2.204.2
Event History
Frequently Asked Questions
What is the severity of CVE-2020-2105?
CVE-2020-2105 has a medium severity rating due to the potential for clickjacking attacks.
How do I fix CVE-2020-2105?
To mitigate CVE-2020-2105, upgrade Jenkins to version 2.219 or later.
Which versions of Jenkins are affected by CVE-2020-2105?
Jenkins versions 2.218 and earlier, including LTS versions 2.204.1 and earlier, are affected by CVE-2020-2105.
What attack vector does CVE-2020-2105 exploit?
CVE-2020-2105 can be exploited through clickjacking attacks that involve embedding REST API endpoints in iframes.
What is the impact of CVE-2020-2105 on Jenkins users?
The impact of CVE-2020-2105 is that it allows attackers to manipulate users into unintentionally interacting with the vulnerable Jenkins REST API.