Jenkins REST APIs vulnerable to clickjacking
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-2105US | medium5.4 | — | ||
REST API endpoints in Jenkins 2.218 and earlier, LTS 2.204.1 and earlier were vulnerable to clickjacking attacks. | ||||
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2020/01/29/1WEB
- https://access.redhat.com/errata/RHBA-2020:0402WEB
- https://access.redhat.com/errata/RHBA-2020:0675WEB
- https://access.redhat.com/errata/RHSA-2020:0681WEB
- https://access.redhat.com/errata/RHSA-2020:0683WEB
- https://github.com/jenkinsci/jenkinsPACKAGE
- https://github.com/jenkinsci/jenkins/commit/639ade55caa05324c60d15b2fa8df27ee0111b76WEB
- https://jenkins.io/security/advisory/2020-01-29/#SECURITY-1704WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan