Config File Provider vulnerabilitiesRanked by how likely they are to be used.
Config File Provider is made by Jenkins. We track 9 published vulnerabilities in it, across 74 versions. None of them is on the list of flaws known to be exploited today. If you run Config File Provider, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Config File Provider vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Config File Provider's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Config File Provider flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 38%CVE-2021-21642High
Jenkins Config File Provider Plugin 3.7.0 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
- 1.1%CVE-2021-21643Medium
Jenkins Config File Provider Plugin 3.7.0 and earlier does not correctly perform permission checks in several HTTP endpoints, allowing attackers with global Job/Configure permission to enumerate system-scoped...
- 1.1%CVE-2021-21644Medium
A cross-site request forgery (CSRF) vulnerability in Jenkins Config File Provider Plugin 3.7.0 and earlier allows attackers to delete configuration files corresponding to an attacker-specified ID.
- 0.9%CVE-2018-1000413Medium
A 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...
- 0.9%CVE-2021-21645Medium
Jenkins Config File Provider Plugin 3.7.0 and earlier does not perform permission checks in several HTTP endpoints, attackers with Overall/Read permission to enumerate configuration file IDs.
- 0.9%CVE-2019-1003014Medium
An cross-site scripting vulnerability exists in Jenkins Config File Provider Plugin 3.4.1 and earlier in src/main/resources/lib/configfiles/configfiles.jelly that allows attackers with permission to define shared...
- 0.8%CVE-2018-1000414High
A 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...
- 0.8%CVE-2017-1000104Medium
The Config File Provider Plugin is used to centrally manage configuration files that often include secrets, such as passwords.
- 0.8%CVE-2023-40339High
Jenkins Config File Provider Plugin 952.va_544a_6234b_46 and earlier does not mask (i.e., replace with asterisks) credentials specified in configuration files when they're written to the build log.
Running Config File Provider? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Jenkins Config File Provider Plugin 3.7.0 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
- Matched to
- Config File Provider on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 9 published vulnerabilities listed under the name Config File Provider, across 74 versions.
None of Config File Provider's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Config File Provider. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.