First published: Wed Jul 17 2019(Updated: )
CSRF tokens in Jenkins 2.185 and earlier, LTS 2.176.1 and earlier did not expire, thereby allowing attackers able to obtain them to bypass CSRF protection.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/jenkins weekly | <2.186 | 2.186 |
redhat/Jenkins LTS | <2.176.2 | 2.176.2 |
Jenkins Jenkins | <=2.176.1 | |
Jenkins Jenkins | <=2.185 | |
maven/org.jenkins-ci.main:jenkins-core | >=2.177<=2.185 | 2.186 |
maven/org.jenkins-ci.main:jenkins-core | <=2.176.1 | 2.176.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-10353 has a medium severity, allowing CSRF protection bypass.
To fix CVE-2019-10353, update Jenkins to version 2.186 or later, or LTS version 2.176.2 or later.
Jenkins versions prior to 2.186 and LTS versions prior to 2.176.2 are affected by CVE-2019-10353.
CVE-2019-10353 is a Cross-Site Request Forgery (CSRF) vulnerability.
Yes, CVE-2019-10353 can be exploited remotely if the attacker obtains the CSRF tokens.