File ParametersApplication · Jenkins
CVE-2023-32986
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 File Parameter Plugin 285.v757c5b_67a_c25 and earlier does not restrict the name (and resulting uploaded file name) of Stashed File Parameters, allowing attackers with Item/Configure permission to create or replace arbitrary files on the Jenkins controller file system with attacker-specified content.
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 · moderate confidenceThe Jenkins File Parameter Plugin fails to validate or restrict file names in Stashed File Parameters, allowing path traversal. Attackers with Item/Configure permission can specify arbitrary file paths in the parameter name field, causing uploaded files to be written to attacker-controlled locations on the Jenkins controller filesystem.
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
File ParametersApplication
<= 285.287.v4b_7b_29d3469dCVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 File Parameter Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed, locate 'File Parameters' plugin, and note the version number. Alternatively, run: Jenkins.instance.pluginManager.getPlugin('file-parameters')?.version in the script consoleAffected if Version is 285.287.v4b_7b_29d3469d or earlier
-
Verify Stashed File Parameter feature usageReview job configurations for any jobs using the 'Stashed File Parameter' parameter type. Check job configuration XML or UI for parameters of type 'StashedFileParameterDefinition'Affected if Jobs are configured to accept Stashed File Parameters as input
-
Check Item/Configure permission scopeReview users or groups with Item/Configure permissions in Manage Jenkins > Security. These permissions allow creating or modifying job configurations containing file parametersAffected if Users or groups have Item/Configure permission and can modify job configurations
-
Inspect filesystem for unexpected filesSearch for files in Jenkins home directory or controller filesystem that were written outside expected job workspace or artifact directories, particularly in the period when untrusted users had configure accessAffected if Files exist in unexpected locations outside normal job workspaces
You are affected if the File Parameter Plugin is installed at version 285.287.v4b_7b_29d3469d or earlier and users with Item/Configure permission can configure jobs using Stashed File Parameters.
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.
dbcve · scopedUpgrade the Jenkins File Parameter Plugin to the latest available version which properly validates and sanitizes Stashed File Parameter names.
285.v757c5b_67a_c25 or later
- Log in to the Jenkins controller as an administrator
- Navigate to 'Manage Jenkins' > 'Manage Plugins'
- Go to the 'Available' tab or 'Updates' tab
- Locate the 'File Parameters' plugin in the plugin list
- If an update is available, select the plugin and click 'Download now and install after restart'
- Alternatively, search for 'File Parameters' in the 'Available' tab and install version 285.v757c5b_67a_c25 or later
- After installation, restart Jenkins to apply the changes
- Verify the plugin is running the fixed version by checking 'Manage Plugins' > 'Installed' tab
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in File Parameters
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-2023-32986 — 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-2023-32986 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