Associated FilesApplication · Jenkins
CVE-2022-45401
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 Associated Files Plugin 0.2.1 and earlier does not escape names of associated files, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/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 Jenkins Associated Files Plugin versions 0.2.1 and earlier fail to properly escape names of associated files when rendering them in the UI, leading to a stored cross-site scripting (XSS) vulnerability. An attacker with Item/Configure permission can embed malicious JavaScript code within a file name that will execute in the browsers of other users viewing the associated files.
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
Associated FilesApplication
<= 0.2.1CVSS 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.
-
Verify if Associated Files plugin is installedCheck the Jenkins plugin directory (typically $JENKINS_HOME/plugins/) for the associated-files-plugin folder, or use the Jenkins script console: Jenkins.instance.pluginManager.plugins.collect { it.shortName }.contains('associated-files-plugin')Affected if The plugin folder exists or the script returns true
-
Determine the installed plugin versionCheck the manifest file within the plugin folder ($JENKINS_HOME/plugins/associated-files-plugin/META-INF/MANIFEST.MF) for the Plugin-Version attribute, or use the script console: Jenkins.instance.pluginManager.plugins.find { it.shortName == 'associated-files-plugin'?.versionAffected if The version is 0.2.1 or earlier
-
Verify if the plugin is actively configuredNavigate to a job's configuration page and check if the 'Associated Files' option is available or configured, or check job config.xml files for <associatedFiles> elementsAffected if The plugin UI element is present and accessible to users with Item/Configure permission
-
Confirm user access to vulnerable UICheck if any users have Item/Configure permissions who could potentially inject malicious file names, or review audit logs for recent job configuration changes involving file associationsAffected if Users with Item/Configure permission exist and can access job configuration
The environment is affected if the Associated Files plugin is installed with version 0.2.1 or earlier and the plugin UI is accessible to users with configuration permissions.
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 Associated Files Plugin to a version that addresses this vulnerability and implements proper output encoding of file names, or remove the plugin if it is not required.
Fix this in Associated Files
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45401 — 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-2022-45401 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