Remote code execution via unrestricted YAML type instantiation
Published Sep 21, 2022 · Updated May 28, 2025
Unsafe YAML deserialization in Jenkins DotCi Plugin 2.40.00 and earlier allows attackers to execute code via crafted .ci.yml files. The plugin's YAML parser permits arbitrary Java type instantiation when it loads repository-controlled .ci.yml configuration. Exploitation requires the ability to modify .ci.yml in a configured SCM repository, after which attacker-controlled code runs on the Jenkins controller.
Summary
What happened
Unsafe YAML deserialization in Jenkins DotCi Plugin 2.40.00 and earlier allows attackers to execute code via crafted .ci.yml files. The plugin's YAML parser permits arbitrary Java type instantiation when it loads repository-controlled .ci.yml configuration. Exploitation requires the ability to modify .ci.yml in a configured SCM repository, after which attacker-controlled code runs on the Jenkins controller.
The record
- CVE
- CVE-2022-41237
- Published
- Sep 21, 2022
- Updated
- May 28, 2025
- Vendor
- Jenkins Project
- Product
- DotCi
- Classifications
- CWE-502
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 21, 2022CVE publishedPublication date reported by the CVE source.
- May 28, 2025Record 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 <=2.40.00
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