Folder Based Authorization StrategyApplication · Jenkins
CVE-2025-24401
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 Folder-based Authorization Strategy Plugin 217.vd5b_18537403e and earlier does not verify that permissions configured to be granted are enabled, potentially allowing users formerly granted (typically optional permissions, like Overall/Manage) to access functionality they're no longer entitled to.
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 Folder-based Authorization Strategy Plugin fails to verify that permissions configured to be granted are actually enabled. This allows users who were previously granted optional permissions (like Overall/Manage) to retain access to functionality they're no longer entitled to, creating an authorization bypass.
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
Folder Based Authorization StrategyApplication
<= 217.vd5b_18537403eCVSS 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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:L
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 Folder-based Authorization Strategy plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Folder-based Authorization Strategy', or inspect the plugin directory $JENKINS_HOME/plugins for a folder-auth-strategy folderAffected if The plugin is present in the Jenkins installation
-
Check the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed tab, locate the Folder-based Authorization Strategy plugin and note the version number. Compare it against the affected range: <= 217.vd5b_18537403eAffected if The version is 217.vd5b_18537403e or earlier
-
Confirm folder-based authorization is the active authorization strategyNavigate to Manage Jenkins > Global Security > Authorization section and verify that 'Folder-based Authorization Strategy' is selected as the current authorization methodAffected if Folder-based Authorization Strategy is enabled as the authorization mechanism
-
Identify if optional permissions were granted to usersIn the folder-based authorization configuration (Manage Jenkins > Configure Global Security or at folder level), review all configured users and groups. Look specifically for optional permissions such as Overall/Manage, Overall/Configure, or other elevated permissions that can be selectively enabledAffected if Any users or groups have optional permissions configured in the authorization strategy
You are affected if the plugin is installed with version 217.vd5b_18537403e or earlier, folder-based authorization is active, and optional permissions have been granted to users who may retain access after those permissions should have been revoked.
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 dataUpdate the Jenkins Folder-based Authorization Strategy Plugin to version 217.vd5b_18537403e or later once available, and verify that user permissions are correctly enforced after the update.
Fix this in Folder Based Authorization Strategy
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24401 — 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-2025-24401 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