CVE-2022-25179 Link Following in Jenkins Pipeline Multibranch Plugin

Medium 6.5 Published Updated

Attackers with Pipeline configuration permissions can read arbitrary files on the Jenkins controller via symbolic link traversal in the readTrusted step.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2022-25179?

CVE-2022-25179 is a medium-severity path traversal vulnerability in Jenkins Pipeline: Multibranch Plugin, published on 15 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-59

Which versions are affected by CVE-2022-25179?

8 open source packages ship an affected version, including org.jenkins-ci.plugins.workflow:workflow-multibranch. It affects 1 product.

PackageAffectedFixed in
org.jenkins-ci.plugins.workflow:workflow-multibranch MavenAll versions2.23.1
org.jenkins-ci.plugins.workflow:workflow-multibranch MavenAll versions2.23.1
org.jenkins-ci.plugins.workflow:workflow-multibranch MavenFrom 2.242.26.1
org.jenkins-ci.plugins.workflow:workflow-multibranch MavenFrom 2.242.26.1
org.jenkins-ci.plugins.workflow:workflow-multibranch MavenFrom 696.v52535c46f4c9696.698.v9b4218eea50f
org.jenkins-ci.plugins.workflow:workflow-multibranch MavenFrom 696.v52535c46f4c9696.698.v9b4218eea50f
2 more packages
org.jenkins-ci.plugins.workflow:workflow-multibranch MavenFrom 706.vd43c65dec013707.v71c3f0a
org.jenkins-ci.plugins.workflow:workflow-multibranch MavenFrom 706.vd43c65dec013707.v71c3f0a

Products include Jenkins Pipeline\.

How do I fix CVE-2022-25179?

Upgrade org.jenkins-ci.plugins.workflow:workflow-multibranch to a fixed version for your release line: 2.23.1, 2.26.1, 696.698.v9b4218eea50f or 707.v71c3f0a.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2022-25179 being exploited?

There is no known exploitation of CVE-2022-25179 in the wild and no public exploit code.

Sources

Also known as GHSA-2m9w-9xh2-wxc3.

Is CVE-2022-25179 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free