CVE-2017-1000104 json
Improper Privilege Management in Jenkins Config File Provider Plugin
published 9y ago modified 4mo ago also GHSA-6h72-m3xw-fp3c , EUVD-2022-2798
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
The Config File Provider Plugin is used to centrally manage configuration files that often include secrets, such as passwords. Users with only Overall/Read access to Jenkins were able to access URLs directly that allowed viewing these files. Access to view these files now requires sufficient permissions to configure the provided files, view the configuration of the folder in which the configuration files are defined, or have Job/Configure permissions to a job able to use these files.
Patch / fix
- maven org.jenkins-ci.plugins:config-file-provider 2.16.2
Is CVE-2017-1000104 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.82% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:config-file-provider | <2.16.2 |
2.16.2 |
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
jenkins.io
/security/advisory/2017-08-07/
vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-1000104
advisory
-
jenkins.io
/security/advisory/2017-08-07
web
Sources
- CVE List CVE-2017-1000104
- GitHub Advisory GHSA-6h72-m3xw-fp3c
- NVD CVE-2017-1000104
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.