Lockable ResourcesApplication · Jenkins
CVE-2020-2281
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 · uneditedA cross-site request forgery (CSRF) vulnerability in Jenkins Lockable Resources Plugin 2.8 and earlier allows attackers to reserve, unreserve, unlock, and reset resources.
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 confidenceA cross-site request forgery (CSRF) vulnerability in Jenkins Lockable Resources Plugin versions 2.8 and earlier allows remote attackers to perform unauthorized actions including reserving, unreserving, unlocking, and resetting lockable resources without the legitimate user's consent. The lack of proper CSRF token validation on state-changing endpoints enables attackers to trick authenticated users into triggering these actions via malicious web pages.
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
Lockable ResourcesApplication
<= 2.8CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 Jenkins is runningAccess the Jenkins dashboard or check the Jenkins service status via system commandsAffected if Jenkins is running with the Lockable Resources plugin installed
-
Confirm Lockable Resources plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and search for 'Lockable Resources', or check the plugin directory for the lockable-resources plugin filesAffected if The Lockable Resources plugin appears in the installed plugins list
-
Check the installed plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed, find Lockable Resources, and note the version number; compare against the affected version rangeAffected if The installed version is 2.8 or earlier (any version <= 2.8)
-
Identify if lockable resources are configuredNavigate to Manage Jenkins > Lockable Resources or check the Jenkins configuration for any defined lockable resourcesAffected if One or more lockable resources are defined in Jenkins configuration
-
Verify state-changing endpoints are accessibleInspect network requests or check the plugin's API endpoints (such as /lockable-resources/reserve, /unreserve, /unlock, /reset) that handle resource state changes; confirm these endpoints lack CSRF token validationAffected if The plugin's state-changing endpoints do not require valid CSRF tokens for requests
A user is affected if Jenkins is running the Lockable Resources plugin at version 2.8 or earlier and lockable resources are configured, as the lack of CSRF protection on resource management endpoints allows unauthorized state changes.
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 the Lockable Resources Plugin to version 2.9 or later which includes CSRF protection tokens. If immediate upgrade is not possible, restrict Jenkins UI access to trusted networks and enforce session management policies.
Fix this in Lockable Resources
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2281 — 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-2020-2281 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