Lockable ResourcesApplication · Jenkins
CVE-2019-1003042
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 scripting vulnerability in Jenkins Lockable Resources Plugin 2.4 and earlier allows attackers able to control resource names to inject arbitrary JavaScript in web pages rendered by the plugin.
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 confidenceThis is a stored cross-site scripting (XSS) vulnerability in Jenkins Lockable Resources Plugin version 2.4 and earlier. Attackers with the ability to control resource names can inject arbitrary JavaScript that executes when other users view resource management pages rendered by the plugin.
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.4CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 Lockable Resources Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for Lockable Resources, or use Jenkins CLI: java -jar jenkins-cli.jar -s http://[JENKINS_URL] list-plugins | grep -i lockableAffected if The Lockable Resources plugin does not appear in the installed plugins list
-
Check installed version of Lockable Resources PluginIn the Jenkins UI Manage Plugins > Installed tab, locate Lockable Resources in the plugin list and note the version number shown in the Version columnAffected if The version displayed is 2.4 or earlier
-
Inspect lockable resource names for injected script contentNavigate to the Lockable Resources management page in Jenkins (typically under Manage Jenkins or a dedicated section), view all configured resource names, and check for any names containing HTML tags, JavaScript code, or script-related keywords like <script, javascript:, onerror, onloadAffected if Any resource name contains executable HTML or JavaScript code that could trigger when other users view the resource page
A user is affected if the Lockable Resources Plugin version is 2.4 or earlier, or if any resource names contain malicious script content.
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 Lockable Resources Plugin to version newer than 2.4. If immediate updating is not feasible, restrict or audit user permissions for creating and modifying resource names as a compensating control.
Fix this in Lockable Resources
Scoped from the published advisory
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003042 — 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-2019-1003042 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