XML file existence disclosure via malformed fingerprint ID
Published Jan 13, 2021 · Updated Aug 3, 2024
Improper input validation in Jenkins 2.274 and earlier and LTS 2.263.1 and earlier allows remote authenticated users to test for XML files. The fingerprint REST endpoint uses a supplied fingerprint ID to form the relative path of XML metadata before enforcing the expected ID format. Overall/Read permission is required, and the oracle reveals only whether an XML file exists when its relative path can be expressed in 32 characters.
Summary
What happened
Improper input validation in Jenkins 2.274 and earlier and LTS 2.263.1 and earlier allows remote authenticated users to test for XML files. The fingerprint REST endpoint uses a supplied fingerprint ID to form the relative path of XML metadata before enforcing the expected ID format. Overall/Read permission is required, and the oracle reveals only whether an XML file exists when its relative path can be expressed in 32 characters.
The record
- CVE
- CVE-2021-21606
- Published
- Jan 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Jenkins
- Classifications
- CWE-20, T1083
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.242 <unspecified
- Affected versionversion=unspecified <=2.274
- Affected versionversion=unspecified <=LTS 2.263.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo