Role Based Authorization StrategyApplication · Jenkins
CVE-2017-1000090
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 · uneditedRole-based Authorization Strategy Plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks. This allowed attackers to add administrator role to any user, or to remove the authorization configuration, preventing legitimate access to Jenkins.
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 Role-based Authorization Strategy Jenkins plugin failed to enforce POST method requirements on its API endpoints, allowing Cross-Site Request Forgery (CSRF) attacks. Attackers could exploit this by tricking authenticated administrators into visiting malicious pages that silently trigger API calls to add administrator roles to arbitrary users or completely remove authorization configuration, locking out legitimate users.
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
Role Based Authorization StrategyApplication
<= 2.5.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Check if Role-based Authorization Strategy plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and look for 'Role-based Authorization Strategy' in the list, or query the plugin manager API at /pluginManager/plugin/{plugin}/api/jsonAffected if The plugin is not listed or not installed - then not affected by this specific plugin vulnerability
-
Identify installed version of Role-based Authorization Strategy pluginIn the installed plugins list, find the version number listed next to 'Role-based Authorization Strategy', or use the API: /pluginManager/plugin/role-strategy/api/jsonAffected if Version is 2.5.0 or lower - this indicates a vulnerable version
-
Verify CSRF protection statusGo to Manage Jenkins > Configure Global Security and locate the 'CSRF Protection' section. Confirm whether 'Enable crumb verification' is checked, or query the security configuration API at /api/json?tree=useCrumbAffected if CSRF protection is disabled or no crumb issuer is configured - this means the CSRF attack vector is fully exposed with no defense in place
-
Check if the vulnerable API endpoints are accessibleTest that POST is required for Role Strategy API endpoints (such as /role-strategy/strategy/assign and /role-strategy/strategy/remove). Attempt a GET request to these endpoints - they should reject GET requests in patched versionsAffected if GET requests to these API endpoints succeed without requiring POST - this indicates the POST requirement is not enforced and the vulnerability is present
A user is affected if the Role-based Authorization Strategy plugin version 2.5.0 or lower is installed AND CSRF protection is disabled, allowing CSRF attacks to modify authorization roles.
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 dataEnable and enforce Jenkins CSRF protection (crumb issuer) for all API requests and upgrade the Role-based Authorization Strategy Plugin to a patched version that requires POST for API endpoints.
Fix this in Role Based Authorization Strategy
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000090 — 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-2017-1000090 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