CVE-2024-52551 — pipeline-model-parent
HIGHCVE-2024-52551 is a high-severity (CVSS 8) Incorrect Default Permissions vulnerability in org.jenkinsci.plugins:pipeline-model-parent. A fix is available for org.jenkinsci.plugins:pipeline-model-parent — see the affected versions and patch details below.
Restarting a run with revoked script approval allowed by Jenkins Pipeline: Declarative Plugin
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-52551.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-52551 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.jenkinsci.plugins:pipeline-model-parentReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins Pipeline: Declarative Plugin 2.2214.vb_b_34b_2ea_9b_83 and earlier does not check whether the main (Jenkinsfile) script used to restart a build from a specific stage is approved, allowing attackers with Item/Build permission to restart a previous build whose (Jenkinsfile) script is no longer approved. This allows attackers with Item/Build permission to restart a previous build whose (Jenkinsfile) script is no longer approved. Pipeline: Declarative Plugin 2.2218.v56d0cda_37c72 refuses to restart a build whose main (Jenkinsfile) script is unapproved.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkinsci.plugins:pipeline-model-parent | all versions | 2.2218.v56d0cdaorg.jenkinsci.plugins:pipeline-model-parent:2.2218.v56d0cda |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkinsci.plugins:pipeline-model-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkinsci.plugins:pipeline-model-parent to 2.2218.v56d0cda or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-52551 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-52551 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-52551. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability is rated as Important due to the risk it poses by allowing attackers with Item/Build permissions to restart a previous build using an unapproved Jenkinsfile script, this could result in unauthorized execution of scripts, compromising the integrity of the build process.
| Product | Fixed in | Advisory |
|---|---|---|
| OCP-Tools-4.12-RHEL-8 | jenkins-0:2.479.3.1740464431-3.el8 | RHSA-2025:2223 |
| OCP-Tools-4.13-RHEL-8 | jenkins-0:2.479.3.1740464433-3.el8 | RHSA-2025:2222 |
| OCP-Tools-4.14-RHEL-8 | jenkins-0:2.479.3.1740109575-3.el8 | RHSA-2025:2221 |
| OCP-Tools-4.15-RHEL-8 | jenkins-0:2.479.3.1740051993-3.el8 | RHSA-2025:2220 |
| OCP-Tools-4.16-RHEL-9 | jenkins-0:2.479.3.1739896390-3.el9 | RHSA-2025:2219 |
| OCP-Tools-4.17-RHEL-9 | jenkins-0:2.479.3.1739859586-3.el9 | RHSA-2025:2218 |
Frequently Asked Questions
Is CVE-2024-52551 in your dependencies?
O3 Security finds CVE-2024-52551 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.