Pipeline\Application · Jenkins
CVE-2024-52551
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Pipeline: Declarative Plugin fails to validate script approval when restarting a build from a specific stage. Attackers with Item/Build permission can restart builds using Jenkinsfiles whose scripts have been revoked or would no longer pass approval, effectively bypassing the script approval sandbox mechanism.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Pipeline\Application
<= 2.2214.vb_b_34b_2ea_9b_83CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Pipeline: Declarative Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: `java -jar jenkins-cli.jar list-plugins | grep 'Pipeline: Declarative'`Affected if Version is 2.2214.vb_b_34b_2ea_9b_83 or lower
-
Confirm Pipeline Declarative jobs existLook for jobs configured to use Pipeline script from SCM or Pipeline script using Jenkinsfile, typically found in job configuration under Pipeline sectionAffected if Jobs are using Pipeline script type with Jenkinsfile-based definitions
-
Verify script approval sandbox is in useNavigate to Manage Jenkins > In-Process Script Approval to see if any scripts are pending, approved, or revokedAffected if Script approval is being used and there are approved or revoked scripts listed
-
Check if builds can be restarted from specific stagesReview job build history; for Pipeline jobs, check if the 'Replay' or 'Restart from Stage' option appears on completed buildsAffected if The environment allows restarting builds from specific stages (not just replaying entire Jenkinsfiles)
You are affected if the Pipeline: Declarative Plugin version is 2.2214.vb_b_34b_2ea_9b_83 or lower AND you have Pipeline jobs using Jenkinsfile-based scripts with script approval enabled AND builds can be restarted from specific stages.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Jenkins Pipeline: Declarative Plugin to the latest version and verify that script approval checks are enforced when restarting builds from specific stages.
Fix this in Pipeline\
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52551 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-52551 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data