This advisory announces vulnerabilities in the following Jenkins deliverables:
Multiple Pipeline-related plugins that perform on-controller SCM checkouts reuse the same workspace directory for checkouts of distinct SCMs in some contexts.
Pipeline: Groovy Plugin 2648.va9433432b33c and earlier uses the same checkout directories for distinct SCMs when reading the script file (typically Jenkinsfile) for Pipelines.
Pipeline: Shared Groovy Libraries 552.vd9cc05b8a2e1 and earlier uses the same checkout directories for distinct SCMs for Pipeline libraries.
Pipeline: Multibranch 706.vd43c65dec013 and earlier uses the same checkout directories for distinct SCMs for the readTrusted step.
This allows attackers with Item/Configure permission to invoke arbitrary OS commands on the controller through crafted SCM contents.
Affected plugins have been updated to address these issues:
Pipeline: Groovy Plugin 2656.vf7a_e7b_75a_457 uses distinct checkout directories per SCM when reading the script file (typically Jenkinsfile) for Pipelines.
Pipeline: Shared Groovy Libraries 561.va_ce0de3c2d69 uses distinct checkout directories per SCM for Pipeline libraries.
Pipeline: Multibranch 707.v71c3f0a_6ccdb_ uses distinct checkout directories per SCM for the readTrusted step.
Multiple Pipeline-related plugins follow symbolic links or do not limit path names, resulting in arbitrary file read vulnerabilities:
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 (originally reported as SECURITY-2595).
Pipeline: Shared Groovy Libraries 552.vd9cc05b8a2e1 and earlier follows symbolic links to locations outside of the expected Pipeline library when reading files using the libraryResource step (originally reported as SECURITY-2479).
Pipeline: Shared Groovy Libraries 552.vd9cc05b8a2e1 and earlier does not restrict the names of resources passed to the libraryResource step (originally reported as SECURITY-2476).
Pipeline: Multibranch 706.vd43c65dec013 and earlier follows symbolic links to locations outside of the checkout directory for the configured SCM when reading files using the readTrusted step (originally reported as SECURITY-2491).
This allows attackers able to configure Pipelines to read arbitrary files on the Jenkins controller file system.
Affected plugins have been updated to address these issues:
Pipeline: Groovy Plugin 2656.vf7a_e7b_75a_457 checks that the script file for Pipelines is inside of the checkout directory for the configured SCM.
Pipeline: Shared Groovy Libraries 561.va_ce0de3c2d69 checks that any resources retrieved by the libraryResource step are contained within the expected Pipeline library.
Pipeline: Multibranch 707.v71c3f0a_6ccdb_ checks that the file retrieved by readTrusted is inside of the checkout directory for the configured SCM.
Pipeline: Groovy Plugin 2648.va9433432b33c and earlier includes password parameters from the original build in replayed builds.
This allows attackers with Run/Replay permission to obtain the values of password parameters passed to previous builds of a Pipeline.
Pipeline: Groovy Plugin 2656.vf7a_e7b_75a_457 does not allow builds containing password parameters to be replayed.
Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier uses the same workspace directory for all checkouts of Pipeline libraries with the same name regardless of the SCM being used and the source of the library configuration.
This allows attackers with Item/Configure permission to execute arbitrary code in the context of the Jenkins controller JVM through crafted SCM contents, if a global Pipeline library already exists.
Pipeline: Shared Groovy Libraries Plugin 561.va_ce0de3c2d69 uses distinct checkout directories per SCM for Pipeline libraries.
Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier uses the names of Pipeline libraries to create directories without canonicalization or sanitization.
This allows attackers with Item/Configure permission to execute arbitrary code in the context of the Jenkins controller JVM using specially crafted library names if a global Pipeline library is already configured.
Pipeline: Shared Groovy Libraries Plugin 561.va_ce0de3c2d69 sanitizes the names of Pipeline libraries when creating library directories.
Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier uses the names of Pipeline libraries to create cache directories without any sanitization.
This allows attackers with Item/Configure permission to execute arbitrary code in the context of the Jenkins controller JVM using specially crafted library names if a global Pipeline library configured to use caching already exists.
Pipeline: Shared Groovy Libraries Plugin 561.va_ce0de3c2d69 sanitizes the names of Pipeline libraries when creating library cache directories.
Pipeline: Build Step Plugin 2.15 and earlier reveals password parameter default values when generating a pipeline script using the Pipeline Snippet Generator.
This allows attackers with Item/Read permission to retrieve the default password parameter value from jobs.
Pipeline: Build Step Plugin 2.15.1 redacts password parameter in the generated pipeline script.
Generic Webhook Trigger Plugin 1.81 and earlier does not escape the build cause for the webhook.
This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to trigger builds using the webhook.
Generic Webhook Trigger Plugin 1.82 escapes the build cause when displayed on the UI.
|
Note
|
This vulnerability is only exploitable in Jenkins 2.314 and earlier, LTS 2.303.1 and earlier. See the LTS upgrade guide. |
HashiCorp Vault Plugin 3.8.0 and earlier implements functionality that allows agent processes to retrieve any Vault secrets for use on the agent.
This allows attackers able to control agent processes to obtain Vault secrets for an attacker-specified path and key.
The functionality that allow agent processes to capture Vault secret can no longer be used in HashiCorp Vault Plugin 336.v182c0fbaaeb7.
Support Core Plugin has a feature to redact potentially sensitive information in the support bundle.
Support Core Plugin 2.79 and earlier does not redact some sensitive information in the support bundle.
This sensitive information can be viewed by anyone with access to the bundle.
Support Core Plugin 2.79.1 adds a list of keywords whose associated values will be redacted.
This list is stored in the security-stop-words.txt file located in $JENKINS_HOME/support and can be amended to add additional keywords for values that should be redacted.
Fortify Plugin 20.2.34 and earlier does not sanitize the appName and appVersion parameters of its Pipeline steps, which are used to write to files inside build directories.
This allows attackers with Item/Configure permission to write or overwrite .xml files on the Jenkins controller file system with content not controllable by the attacker.
Fortify Plugin 20.2.35 sanitizes the appName and appVersion parameters of its Pipeline steps when determining the resulting filename.
Custom Checkbox Parameter Plugin 1.1 and earlier does not escape parameter names of custom checkbox parameters.
This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.
Custom Checkbox Parameter Plugin 1.2 escapes parameter names of custom checkbox parameters.
Conjur Secrets Plugin 1.0.11 and earlier does not perform a permission check in an HTTP endpoint.
This allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins. Those can be used as part of an attack to capture the credentials using another vulnerability.
An enumeration of credentials IDs in Conjur Secrets Plugin 1.0.12 requires Overall/Administer permission.
Agent Server Parameter Plugin 1.0 and earlier does not escape parameter names of agent server parameters.
This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.
Agent Server Parameter Plugin 1.1 escapes parameter names of agent server parameters.
Snow Commander Plugin 2.0 and earlier does not perform permission checks in methods implementing form validation.
This allows attackers with Overall/Read permission to connect to an attacker-specified webserver using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Additionally, these form validation methods do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
Snow Commander Plugin 2.0 requires POST requests and Overall/Administer permission for the affected form validation methods.
autonomiq Plugin 1.15 and earlier does not perform a permission check in an HTTP endpoint.
This allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified username and password.
Additionally, this HTTP endpoint does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
autonomiq Plugin 1.16 requires POST requests and Overall/Administer permission for this HTTP endpoint.
GitLab Authentication Plugin 1.13 and earlier records the HTTP Referer header as part of the URL query parameters when the authentication process starts and redirects users to that URL when the user has finished logging in.
This allows attackers with access to Jenkins to craft a URL that will redirect users to an attacker-specified URL after logging in.
|
Note
|
This issue is caused by an incomplete fix of SECURITY-796. |
As of publication of this advisory, there is no fix.
HashiCorp Vault Plugin 336.v182c0fbaaeb7 and earlier implements functionality that allows agent processes to read arbitrary files on the Jenkins controller file system.
This allows attackers able to control agent processes to read arbitrary files on the Jenkins controller file system.
|
Note
|
This vulnerability is only exploitable in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier. See the LTS upgrade guide. |
As of publication of this advisory, there is no fix.
SCP publisher Plugin 1.8 and earlier does not perform a permission check in a method implementing form validation.
This allows attackers with Overall/Read permission to connect to an attacker-specified SSH server using attacker-specified username and password.
Additionally, this form validation method does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
As of publication of this advisory, there is no fix.
Checkmarx Plugin 2022.1.2 and earlier does not perform permission checks in several HTTP endpoints.
This allows attackers with Overall/Read permission to connect to an attacker-specified webserver using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Additionally, these HTTP endpoints do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
As of publication of this advisory, there is no fix.
Promoted Builds (Simple) Plugin 1.9 and earlier does not escape the name of custom promotion levels.
This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Overall/Administer permission.
As of publication of this advisory, there is no fix.
Team Views Plugin 0.9.0 and earlier does not escape team names.
This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Overall/Read permission.
As of publication of this advisory, there is no fix.
Doktor Plugin 0.4.1 and earlier implements functionality that allows agent processes to render files on the controller as Markdown or Asciidoc.
Additionally, error messages allow attackers able to control agent processes to determine whether a file with a given name exists.
As of publication of this advisory, there is no fix.
dbCharts Plugin 0.5.2 and earlier does not perform a permission check in a method implementing form validation.
This allows attackers with Overall/Read permission to connect to an attacker-specified database via JDBC using attacker-specified credentials.
Additionally, this method allows attackers to determine whether a class is available on the Jenkins controller’s class path through error messages.
Additionally, this form validation method does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
As of publication of this advisory, there is no fix.
Chef Sinatra Plugin 1.20 and earlier does not perform a permission check in a method implementing form validation.
This allows attackers with Overall/Read permission to have Jenkins send an HTTP request to an attacker-controlled URL and have it parse the response as XML.
As the plugin does not configure its XML parser to prevent XML external entity (XXE) attacks, attackers can have Jenkins parse a crafted XML response that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery.
Additionally, this form validation method does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
As of publication of this advisory, there is no fix.
Convertigo Mobile Platform Plugin 1.1 and earlier uses static fields to store job configuration information.
This allows attackers with Item/Configure permission to capture passwords of the jobs that will be configured.
As of publication of this advisory, there is no fix.
SWAMP Plugin 1.2.6 and earlier does not perform a permission check in a method implementing form validation.
This allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Additionally, this form validation method does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
As of publication of this advisory, there is no fix.
These versions include fixes to the vulnerabilities described above. All prior versions are considered to be affected by these vulnerabilities unless otherwise indicated.
As of publication of this advisory, no fixes are available for the following plugins:
The Jenkins project would like to thank the reporters for discovering and reporting these vulnerabilities: