CVE-2022-25178: Path Traversal
A flaw was found in Jenkins. The Pipeline: Shared Groovy Libraries does not restrict the names of resources passed to the libraryResource step. This flaw allows attackers who can configure Pipelines to read arbitrary files on the Jenkins controller file system.
Other sources
Jenkins Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier does not restrict the names of resources passed to the libraryResource step, allowing attackers able to configure Pipelines permission to read arbitrary files on the Jenkins controller file system.
Jenkins Pipeline: Shared Groovy Libraries Plugin does not restrict the names of resources passed to the libraryResource step, allowing attackers able to configure Pipelines permission to read arbitrary files on the Jenkins controller file system.
Pipeline: Shared Groovy Libraries 552.vd9cc05b8a2e1 and earlier does not restrict the names of resources passed to the libraryResource step. This allows attackers able to configure Pipelines to read arbitrary files on the Jenkins controller file system.
References:
https://www.jenkins.io/security/advisory/2022-02-15/
— Red Hat
Affected Software
Remediation
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2022-25178?
CVE-2022-25178 is rated as a high severity vulnerability due to its potential to expose sensitive files on the Jenkins controller.
How do I fix CVE-2022-25178?
To remediate CVE-2022-25178, upgrade the Pipeline: Shared Groovy Libraries to version 2.18.1 or the appropriate version specified in the advisory.
What impact does CVE-2022-25178 have on Jenkins security?
CVE-2022-25178 allows attackers to exploit the Pipeline: Shared Groovy Libraries and read arbitrary files from the Jenkins file system, posing a significant security risk.
Which versions of Jenkins are affected by CVE-2022-25178?
CVE-2022-25178 affects versions of Jenkins prior to 2.18.1 and specific versions in the 2.19 to 2.21.1 range.
What should I do if I can't upgrade to fix CVE-2022-25178?
If an upgrade is not possible, consider restricting access to pipeline configurations and monitoring for unauthorized changes to mitigate the risk associated with CVE-2022-25178.