Controller code execution via unsanitized library cache names
Published Feb 15, 2022 · Updated Aug 3, 2024
Sandbox bypass in Pipeline: Shared Groovy Libraries 552.vd9cc05b8a2e1 and earlier allows remote authenticated users to execute controller code. Unsanitized library names are used directly to form cache-directory paths, letting crafted names escape the intended library cache location. Exploitation requires Item/Configure permission and an existing global Pipeline library configured to use caching, after which code runs in the Jenkins controller JVM.
Summary
What happened
Sandbox bypass in Pipeline: Shared Groovy Libraries 552.vd9cc05b8a2e1 and earlier allows remote authenticated users to execute controller code. Unsanitized library names are used directly to form cache-directory paths, letting crafted names escape the intended library cache location. Exploitation requires Item/Configure permission and an existing global Pipeline library configured to use caching, after which code runs in the Jenkins controller JVM.
The record
- CVE
- CVE-2022-25183
- Published
- Feb 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Pipeline: Groovy Libraries
- Classifications
- T1190
- 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=2.21 <unspecified
- 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