Locked Files ReportApplication · Jenkins
CVE-2020-2271
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 Locked Files Report Plugin 1.6 and earlier does not escape locked files' names in tooltips, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Job/Configure permission.
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 Locked Files Report Plugin versions 1.6 and earlier fails to escape HTML special characters in locked file names when rendering tooltips. An attacker with Job/Configure permission can embed malicious JavaScript code within a file name, which gets stored and executed in the browsers of other users viewing the affected tooltips.
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
Locked Files ReportApplication
<= 1.6CVSS 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.1/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.
-
Confirm Locked Files Report plugin is installedNavigate to Jenkins plugin management (Manage Jenkins > Manage Plugins) and look for the Locked Files Report plugin in the Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-pluginsAffected if The plugin appears in the list of installed plugins
-
Determine installed plugin versionIn the Installed plugins list, locate the Locked Files Report plugin and note its version number from the Version columnAffected if The installed version is 1.6 or lower (for example, 1.6, 1.5, 1.4, etc.)
-
Check if the plugin tooltip feature is accessibleAccess the Locked Files Report view (typically found on the left side of job or project pages where locked files are tracked) and hover over any file entries to see if tooltips are renderedAffected if Tooltips are displayed when hovering over locked file names and the plugin version is 1.6 or earlier
-
Identify users with Job/Configure permissionReview Jenkins authorization matrix or project-based permissions to see which users or groups have Job/Configure permission on the affected jobs or projectsAffected if There are users granted Job/Configure permission beyond trusted administrators and the plugin version is 1.6 or earlier
You are affected if the Locked Files Report plugin is installed with version 1.6 or earlier and the tooltip feature is being used, allowing any user with Job/Configure permission to inject malicious scripts into file names that execute in other users browsers.
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 Locked Files Report Plugin to version 1.7 or later which contains the fix for proper output encoding. Until the update is applied, limit Job/Configure permission to trusted administrators only.
Fix this in Locked Files Report
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-2020-2271 — 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-2271 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