Authenticated file read via libraryResource symlinks
Published Feb 15, 2022 · Updated Aug 3, 2024
Arbitrary file read in Jenkins Pipeline: Groovy Libraries 552.vd9cc05b8a2e1 and earlier allows remote authenticated users to read controller files. The libraryResource step follows resource symlinks without verifying that the resolved path remains inside the expected Pipeline library. Item/Configure permission and the ability to configure a Pipeline are required; successful exploitation discloses arbitrary controller files.
Summary
What happened
Arbitrary file read in Jenkins Pipeline: Groovy Libraries 552.vd9cc05b8a2e1 and earlier allows remote authenticated users to read controller files. The libraryResource step follows resource symlinks without verifying that the resolved path remains inside the expected Pipeline library. Item/Configure permission and the ability to configure a Pipeline are required; successful exploitation discloses arbitrary controller files.
The record
- CVE
- CVE-2022-25177
- Published
- Feb 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Pipeline: Groovy Libraries
- Classifications
- CWE-59, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 15, 2022CVE 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=unspecified <=552.vd9cc05b8a2e1
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.
Weakness, pattern, technique
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