Conversation
Generic path-construction shape: FilePath.toURI().resolve(non-literal) can escape the workspace via leading-slash or .. segments, and is commonly followed by controller-side java.io.File I/O.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Detects
FilePath.toURI().resolve(...)with a non-literal argument.URI.resolvetreats a leading slash as an absolute URI path and collapses..segments, so a job-configured folder string can escape the intended workspace. Callers often pass the resulting path tojava.io.File, which resolves on the Jenkins controller rather than the agent that owns theFilePath.Pattern (generic)
workspace.toURI().resolve(rel)whererelis not a string literalresolve("...")is excludedTest
workspace.toURI().resolve(outputFolder)firesworkspace.toURI().resolve("features")does not fireNo vendor, plugin, file path, or exploit details.