Pipeline behavior modification via untrusted library retrieval
Published Apr 12, 2022 · Updated Nov 20, 2024
Incorrect authorization in Jenkins Pipeline: Groovy Libraries 564.ve62a_4eb_b_e039 and earlier allows remote attackers to alter Pipeline behavior. The library step fails to apply the multibranch trust check when its retriever selects a library from the current build's repository and branch. Exploitation requires permission to submit a pull request without direct commit access and lets untrusted library changes control the resulting Pipeline behavior.
Summary
What happened
Incorrect authorization in Jenkins Pipeline: Groovy Libraries 564.ve62a_4eb_b_e039 and earlier allows remote attackers to alter Pipeline behavior. The library step fails to apply the multibranch trust check when its retriever selects a library from the current build's repository and branch. Exploitation requires permission to submit a pull request without direct commit access and lets untrusted library changes control the resulting Pipeline behavior.
The record
- CVE
- CVE-2022-29047
- Published
- Apr 12, 2022
- Updated
- Nov 20, 2024
- Vendor
- Jenkins Project
- Product
- Pipeline: Groovy Libraries
- Classifications
- CWE-863, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 12, 2022CVE publishedPublication date reported by the CVE source.
- Nov 20, 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 <=564.ve62a_4eb_b_e039
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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