Improper Link Resolution Before File Access in Jenkins Pipeline: Groovy Plugin
Jenkins project Jenkins Pipeline: Groovy Plugin
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.jenkins-ci.plugins.workflow:workflow-cps Maven |
|
|
Jenkins project Jenkins Pipeline: Groovy Plugin
| Product | Affected | Fixed in |
|---|---|---|
| org.jenkins-ci.plugins.workflow:workflow-cps Maven |
|
|
Jenkins Pipeline: Groovy Plugin 2648.va9433432b33c and earlier follows symbolic links to locations outside of the checkout directory for the configured SCM when reading the script file (typically Jenkinsfile) for Pipelines, allowing attackers able to configure Pipelines to read arbitrary files on the Jenkins controller file system.
From the CVE record · jenkins
Jenkins Pipeline: Groovy Plugin 2648.va9433432b33c and earlier follows symbolic links outside the configured SCM checkout when reading a Pipeline script file, typically a Jenkinsfile. An attacker able to configure Pipelines can use this behavior to read arbitrary files on the Jenkins controller file system.
Operators of Jenkins Pipeline: Groovy Plugin 2648.va9433432b33c and earlier should check their org.jenkins-ci.plugins.workflow:workflow-cps package against the affected ranges: >=2.93 <2.94.1, <2.92.1, and >=2.95 <2648.2651.v230593e03e9f.