Revoked Jenkinsfile execution via missing rebuild approval check
Published Nov 13, 2024 · Updated Nov 26, 2024
Approval bypass in Jenkins Pipeline: Groovy allows remote authenticated users to rebuild scripts after their approval is revoked. The rebuild path reuses the main Jenkinsfile without rechecking Script Security approval after an administrator revokes it. Item/Build permission and a previously approved, later-revoked Jenkinsfile are required, enabling that script to execute in a new build.
Summary
What happened
Approval bypass in Jenkins Pipeline: Groovy allows remote authenticated users to rebuild scripts after their approval is revoked. The rebuild path reuses the main Jenkinsfile without rechecking Script Security approval after an administrator revokes it. Item/Build permission and a previously approved, later-revoked Jenkinsfile are required, enabling that script to execute in a new build.
The record
- CVE
- CVE-2024-52550
- Published
- Nov 13, 2024
- Updated
- Nov 26, 2024
- Vendor
- Jenkins Project
- Product
- Pipeline: Groovy
- Classifications
- CWE-354, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 13, 2024CVE publishedPublication date reported by the CVE source.
- Nov 26, 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=0 <=3975.v567e2a_1ffa_22
- Affected versionversion=3990.vd281dd77a_388
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