Cross-Site Request Forgery in Jenkins

2022-05-1401:04:36

Google

osv.dev

0.001 Low

EPSS

Percentile

44.7%

JSON

A race condition during Jenkins 2.94 and earlier; 2.89.1 and earlier startup could result in the wrong order of execution of commands during initialization. There is a very short window of time after startup during which Jenkins may no longer show the ‘Please wait while Jenkins is getting ready to work’ message but Cross-Site Request Forgery (CSRF) protection may not yet be effective.

CPENameOperatorVersion
org.jenkins-ci.main:jenkins-coreeq2.85
org.jenkins-ci.main:jenkins-coreeq2.88
org.jenkins-ci.main:jenkins-coreeq2.92
org.jenkins-ci.main:jenkins-coreeq2.82
org.jenkins-ci.main:jenkins-coreeq2.86
org.jenkins-ci.main:jenkins-coreeq2.91
org.jenkins-ci.main:jenkins-coreeq2.87
org.jenkins-ci.main:jenkins-coreeq2.83
org.jenkins-ci.main:jenkins-coreeq2.94
org.jenkins-ci.main:jenkins-coreeq2.81

Name	Operator	Version
org.jenkins-ci.main:jenkins-core	eq	2.85
org.jenkins-ci.main:jenkins-core	eq	2.88
org.jenkins-ci.main:jenkins-core	eq	2.92
org.jenkins-ci.main:jenkins-core	eq	2.82
org.jenkins-ci.main:jenkins-core	eq	2.86
org.jenkins-ci.main:jenkins-core	eq	2.91
org.jenkins-ci.main:jenkins-core	eq	2.87
org.jenkins-ci.main:jenkins-core	eq	2.83
org.jenkins-ci.main:jenkins-core	eq	2.94
org.jenkins-ci.main:jenkins-core	eq	2.81