Config File ProviderApplication · Jenkins
CVE-2018-1000413
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 exists in Jenkins Config File Provider Plugin 3.1 and earlier in configfiles.jelly, providerlist.jelly that allows users with the ability to configure configuration files to insert arbitrary HTML into some pages in Jenkins.
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 stored cross-site scripting vulnerability in Jenkins Config File Provider Plugin versions 3.1 and earlier allows authenticated users with permission to configure configuration files to inject arbitrary HTML/JavaScript through the configfiles.jelly and providerlist.jelly template files, which is then rendered in Jenkins pages without proper sanitization.
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
Config File ProviderApplication
<= 3.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 Config File Provider Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Config File Provider', or check the plugins directory for config-file-provider folder and its manifestAffected if Plugin is present in the Jenkins installation
-
Determine installed plugin versionIn the Installed Plugins list, locate Config File Provider and note the Version column, or read the manifest.xml file in the plugin directoryAffected if Version is 3.1 or earlier (e.g., 3.1, 3.0, 2.x)
-
Identify users with config file management permissionNavigate to Manage Jenkins > Manage and Assign Users and review which users or groups have the 'Configuration File Provider: Configure' permission enabledAffected if Any authenticated users or groups have permission to configure configuration files
-
Verify vulnerable template files existCheck the plugin directory (typically $JENKINS_HOME/plugins/config-file-provider/) for the presence of configfiles.jelly and providerlist.jelly files in the webapp folderAffected if Both configfiles.jelly and providerlist.jelly files exist in the plugin directory
If Config File Provider plugin version is 3.1 or earlier AND users exist with permission to configure configuration files, the environment is affected by this stored XSS vulnerability.
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 Jenkins Config File Provider Plugin to version 3.2 or later which contains the patch for this XSS vulnerability, or limit and audit user permissions for configuration file management.
Fix this in Config File Provider
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000413 — 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-2018-1000413 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