Shared Library Version OverrideApplication · Jenkins
CVE-2024-52554
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 Shared Library Version Override Plugin 17.v786074c9fce7 and earlier declares folder-scoped library overrides as trusted, so that they're not executed in the Script Security sandbox, allowing attackers with Item/Configure permission on a folder to configure a folder-scoped library override that runs without sandbox protection.
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 Shared Library Version Override Plugin versions 17.v786074c9fce7 and earlier incorrectly declares folder-scoped library overrides as 'trusted', causing them to execute outside the Script Security sandbox. Attackers with Item/Configure permission on a folder can configure a malicious library override to run arbitrary code without sandbox restrictions.
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
Shared Library Version OverrideApplication
<= 17.v786074c9fce7CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Verify the Shared Library Version Override Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and search for 'Shared Library Version Override', or inspect the plugin directory (JENKINS_HOME/plugins/) for the version metadata fileAffected if The plugin is installed with version 17.v786074c9fce7 or earlier
-
Identify folders with library overrides configuredReview each folder in Jenkins and inspect its configuration for any 'Library' or 'Version Override' settings under the folder's Configure page, or use Jenkins CLI/API to list all folder-level library configurationsAffected if Any folder contains a scoped library override configuration
-
Check who has Item/Configure permission on foldersNavigate to each folder's security configuration (Folder > Configure > Permissions) or review global matrix-based security settings to list users/groups with Item/Configure or Extended Read permission on foldersAffected if Users or groups beyond trusted administrators have Item/Configure permission on folders containing library overrides
-
Audit library override configurations for unexpected scriptsInspect each folder-scoped library override's 'Library' and 'Version' fields for references to untrusted or external repositories, or look for overrides that load scripts from non-internal sourcesAffected if Any folder-scoped library override points to an unfamiliar repository or contains version references not recognized by your organization
A user is affected if the Shared Library Version Override Plugin version 17.v786074c9fce7 or earlier is installed AND any folder contains a scoped library override AND users with Item/Configure permission on that folder are not fully trusted.
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 to version 18 or later which properly enforces sandbox restrictions on folder-scoped library overrides. Audit existing folder-scoped library overrides for any unauthorized or unexpected configurations.
Fix this in Shared Library Version Override
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.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-52554 — 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-52554 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