# CVE-2024-52550: Rebuilding a run with revoked script approval allowed by Jenkins Pipeline: Groovy Plugin

> Attackers with build permissions can bypass script approval checks to execute unapproved Groovy code during build rebuilds.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Nov 2024
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-mrpr-vr82-x88r

## What is CVE-2024-52550?

CVE-2024-52550 is a high-severity vulnerability in Jenkins Pipeline: Groovy Plugin, published on 13 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Jenkins Pipeline: Groovy Plugin 3990.vd281dd77a_388 and earlier, except 3975.3977.v478dd9e956c3 does not check whether the main (Jenkinsfile) script for a rebuilt build is approved, allowing attackers with Item/Build permission to rebuild a previous build whose (Jenkinsfile) script is no longer approved.

Weakness: CWE-354 (Improper Validation of Integrity Check Value)

## Which versions are affected by CVE-2024-52550?

2 open source packages ship an affected version, including org.jenkins-ci.plugins.workflow:workflow-cps. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins.workflow:workflow-cps` | Maven | All versions | 3993.v3e20a |
| `org.jenkins-ci.plugins.workflow:workflow-cps` | Maven | All versions | 3993.v3e20a |

Products: Jenkins Pipeline\.

## How do I fix CVE-2024-52550?

Upgrade org.jenkins-ci.plugins.workflow:workflow-cps to 3993.v3e20a or later.

## Is CVE-2024-52550 being exploited?

There is no known exploitation of CVE-2024-52550 in the wild and no public exploit code.

Public exploit code:

- CVE-2024-52550 (github_poc): https://github.com/Anton-ai111/CVE-2024-52550

## Other vulnerabilities in Jenkins Pipeline: Groovy Plugin

- [CVE-2019-1003030](https://insights.sbomify.com/CVE-2019-1003030/): Jenkins Matrix Project Plugin Remote Code Execution (critical 9.9, exploited in the wild)
- [CVE-2022-43402](https://insights.sbomify.com/CVE-2022-43402/): Jenkins Pipeline: Groovy Plugin allows sandbox protection bypass and arbitrary code execution (critical 9.9)
- [CVE-2019-1003041](https://insights.sbomify.com/CVE-2019-1003041/): Sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin (critical 9.8)
- [CVE-2022-43407](https://insights.sbomify.com/CVE-2022-43407/): CSRF protection for any URL can be bypassed in Jenkins Pipeline: Input Step Plugin (high 8.8)
- [CVE-2022-25173](https://insights.sbomify.com/CVE-2022-25173/): Improper Neutralization of Special Elements used in an OS Command in Jenkins Pipeline: Groovy Plugin (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52550 and fix it if it is affected.

What it is: CVE-2024-52550 is a high-severity vulnerability in Jenkins Pipeline: Groovy Plugin, published on 13 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-52550 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins.workflow:workflow-cps (Maven): affected all versions; fixed in 3993.v3e20a
- org.jenkins-ci.plugins.workflow:workflow-cps (Maven): affected all versions; fixed in 3993.v3e20a

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-52550/ (Markdown: https://insights.sbomify.com/CVE-2024-52550/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-52550
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-52550
- OSV: https://osv.dev/vulnerability/CVE-2024-52550

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-52550/
Summaries are generated and may contain mistakes; the official description above is the record.