Improper Limitation of a Pathname to a Restricted Directory in Jenkins
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.jenkins-ci.main:jenkins-core Maven |
|
|
| org.kohsuke.stapler:stapler-parent Maven |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| org.jenkins-ci.main:jenkins-core Maven |
|
|
| org.kohsuke.stapler:stapler-parent Maven |
|
|
A path traversal vulnerability exists in the Stapler web framework used by Jenkins 2.145 and earlier, LTS 2.138.1 and earlier in core/src/main/java/org/kohsuke/stapler/Facet.java, groovy/src/main/java/org/kohsuke/stapler/jelly/groovy/GroovyFacet.java, jelly/src/main/java/org/kohsuke/stapler/jelly/JellyFacet.java, jruby/src/main/java/org/kohsuke/stapler/jelly/jruby/JRubyFacet.java, jsp/src/main/java/org/kohsuke/stapler/jsp/JSPFacet.java that allows attackers to render routable objects using any view in Jenkins, exposing internal information about those objects not intended to be viewed, such as their toString() representation.
From the CVE record · mitre
A path traversal flaw in the Stapler web framework used by Jenkins can let attackers render routable objects with views not intended for them, exposing internal information such as an object's toString() representation. The input does not specify whether authentication or user interaction is required.
Check deployments using Maven packages org.jenkins-ci.main:jenkins-core before 2.138.2 or from 2.140 up to but not including 2.146, or org.kohsuke.stapler:stapler-parent before 1.250.2.