Controller command execution via reused SCM checkout directories
Published Feb 15, 2022 · Updated Aug 3, 2024
OS command injection in Jenkins Pipeline: Groovy Plugin 2648.va9433432b33c and earlier allows remote authenticated users to run controller commands. When reading a Pipeline script, the plugin reuses one controller checkout directory for distinct SCMs, allowing crafted contents from one SCM to control the Jenkinsfile loaded for another. Item/Configure permission and control of SCM contents are required; successful exploitation executes arbitrary OS commands in the controller context.
Summary
What happened
OS command injection in Jenkins Pipeline: Groovy Plugin 2648.va9433432b33c and earlier allows remote authenticated users to run controller commands. When reading a Pipeline script, the plugin reuses one controller checkout directory for distinct SCMs, allowing crafted contents from one SCM to control the Jenkinsfile loaded for another. Item/Configure permission and control of SCM contents are required; successful exploitation executes arbitrary OS commands in the controller context.
The record
- CVE
- CVE-2022-25173
- Published
- Feb 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Pipeline: Groovy
- Classifications
- CWE-78, T1059
- 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 <=2648.va9433432b33c
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