GHSA-f585-9fw3-rj2m
Arbitrary file existence check in file fingerprints in Jenkins
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Maven | org.jenkins-ci.main:jenkins-core | < 2.263.2 | 2.263.2 |
| Maven | org.jenkins-ci.main:jenkins-core | >= 2.264, < 2.275 | 2.275 |
Details
As written in the advisory (Markdown source, shown as plain text).
Jenkins provides a feature for jobs to store and track fingerprints of files used during a build. Jenkins 2.274 and earlier, LTS 2.263.1 and earlier provides a REST API to check where a given fingerprint was used by which builds. This endpoint does not fully validate that the provided fingerprint ID is properly formatted before checking for the XML metadata for that fingerprint on the controller file system.
This allows attackers with Overall/Read permission to check for the existence of XML files on the controller file system where the relative path can be constructed as 32 characters.
Jenkins 2.275, LTS 2.263.2 validates that a fingerprint ID is properly formatted before checking for its existence.
References
External links from the advisory. They lead to third-party sites.