GitHub Advisoryadvisory · Maven
GHSA-f585-9fw3-rj2m Arbitrary file existence check in file fingerprints in Jenkins
MEDIUM
Official page ↗
- Aliases
- CVE-2021-21606
- Ecosystem
- Maven
- Packages
- org.jenkins-ci.main:jenkins-core
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- Weaknesses
- CWE-20
- Reviewed
- 2022-06-23
Affected packages
• Maven org.jenkins-ci.main:jenkins-core: < 2.263.2 → fixed in 2.263.2
• Maven org.jenkins-ci.main:jenkins-core: >= 2.264, < 2.275 → fixed in 2.275
Description
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.
Related
Alias · CVE (1)
- CVE-2021-21606 Jenkins 2.274 and earlier, LTS 2.263.1 and earlier improperly validates the format of a provided fingerprint ID when checking for its… vulnerability
Weakness · CWE (1)
- CWE-20 Improper Input Validation weakness