Config File ProviderApplication · Jenkins
CVE-2018-1000414
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 request forgery vulnerability exists in Jenkins Config File Provider Plugin 3.1 and earlier in ConfigFilesManagement.java, FolderConfigFileAction.java that allows creating and editing configuration file definitions.
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 confidenceCross-site request forgery vulnerability in Jenkins Config File Provider Plugin 3.1 and earlier allows attackers to create and edit configuration file definitions by tricking authenticated users into visiting malicious URLs. The affected components are ConfigFilesManagement.java and FolderConfigFileAction.java which lack proper CSRF token validation.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Verify Jenkins is runningAccess the Jenkins web interface or check for Jenkins process (e.g., ps aux | grep jenkins or netstat -nlp | grep 8080)Affected if Jenkins is running and accessible on the network
-
Identify Config File Provider Plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Config File Provider', or use: jenkins-cli.jar or REST API: /pluginManager/plugin/config-file-provider/api/json?pretty=trueAffected if The installed version is 3.1 or earlier (the vulnerable versions)
-
Confirm plugin is enabledIn Jenkins UI, go to Manage Jenkins > Configure System and look for 'Config File Provider' section, or check if the '/configureConfigFiles' endpoint is accessibleAffected if The plugin is installed and enabled, making the CSRF-protected endpoints available
You are affected if Jenkins is running with Config File Provider Plugin version 3.1 or earlier and the plugin is enabled, as the lack of CSRF protection in ConfigFilesManagement.java and FolderConfigFileAction.java allows unauthorized configuration file modifications.
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 Jenkins Config File Provider Plugin to version 3.2 or later which includes CSRF protection. Alternatively, ensure Jenkins administrators are not logged in when browsing untrusted sites to reduce exposure.
Fix this in Config File Provider
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000414 — 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-1000414 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