CVE-2022-25179: Medium severity jenkins pipeline vulnerability
A flaw was found in Jenkins. The Pipeline: Multibranch follows symbolic links to locations outside of the checkout directory for the configured SCM when reading files using the readTrusted step. This flaw allows attackers that can configure Pipelines, to read arbitrary files on the Jenkins controller file system.
Other sources
Jenkins Pipeline: Multibranch Plugin 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, allowing attackers able to configure Pipelines permission to read arbitrary files on the Jenkins controller file system.
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. 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-25179?
CVE-2022-25179 is considered a high severity vulnerability due to its potential to allow unauthorized file access.
How do I fix CVE-2022-25179?
To fix CVE-2022-25179, upgrade to the Jenkins Pipeline: Multibranch Plugin version 707 or later.
What type of attack can occur due to CVE-2022-25179?
CVE-2022-25179 allows attackers with Pipeline permissions to read arbitrary files outside of the checkout directory.
Which Jenkins versions are affected by CVE-2022-25179?
Jenkins Pipeline: Multibranch Plugin versions up to and including 706.vd43c65dec013 are affected.
Is there a workaround for CVE-2022-25179 while a fix is being implemented?
There is no official workaround for CVE-2022-25179; upgrading to a fixed version is the recommended action.