First published: Wed Jan 29 2020(Updated: )
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.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins Jenkins | <=2.204.1 | |
Jenkins Jenkins | <=2.218 | |
maven/org.jenkins-ci.main:jenkins-core | >=2.205<=2.218 | 2.219 |
maven/org.jenkins-ci.main:jenkins-core | <=2.204.1 | 2.204.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-2105 has a medium severity rating due to the potential for clickjacking attacks.
To mitigate CVE-2020-2105, upgrade Jenkins to version 2.219 or later.
Jenkins versions 2.218 and earlier, including LTS versions 2.204.1 and earlier, are affected by CVE-2020-2105.
CVE-2020-2105 can be exploited through clickjacking attacks that involve embedding REST API endpoints in iframes.
The impact of CVE-2020-2105 is that it allows attackers to manipulate users into unintentionally interacting with the vulnerable Jenkins REST API.