{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:config-file-provider. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000104 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:config-file-provider to 2.16.2 or later.","what":"CVE-2017-1000104 is a medium-severity missing authorization vulnerability in n/a, published on 4 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1000104 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000104 is a medium-severity missing authorization vulnerability in n/a, published on 4 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-1000104 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:config-file-provider (Maven): affected all versions; fixed in 2.16.2\n- org.jenkins-ci.plugins:config-file-provider (Maven): affected all versions; fixed in 2.16.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-1000104/ (Markdown: https://insights.sbomify.com/CVE-2017-1000104/index.md)","id":"CVE-2017-1000104","markdown":"https://insights.sbomify.com/CVE-2017-1000104/index.md","name":"CVE-2017-1000104","record":{"aliases":["GHSA-6h72-m3xw-fp3c"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Users with read-only access could view sensitive configuration files containing secrets due to missing authorization checks in the Config File Provider Plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"config_file_provider","vendor":"jenkins"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Privilege Management in Jenkins Config File Provider Plugin","id":"CVE-2017-1000104","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2017"},"n_packages":2,"n_references":1,"next":{"headline":"Missing Authorization in Jenkins Blue Ocean Plugin","id":"CVE-2017-1000105"},"packages":[{"ecosystem":"Maven","fixed":["2.16.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:config-file-provider","purl":null,"source":"GHSA-6h72-m3xw-fp3c"},{"ecosystem":"Maven","fixed":["2.16.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:config-file-provider","purl":"pkg:maven/org.jenkins-ci.plugins/config-file-provider","source":"GHSA-6h72-m3xw-fp3c"}],"prev":{"headline":"Persistent XSS vulnerability in Jenkins DRY Plugin","id":"CVE-2017-1000103"},"products":["n/a"],"published":"2017-10-04","related":[{"cvss_score":8.1,"headline":"XML External Entity Reference vulnerability in Jenkins Config File Provider Plugin","id":"CVE-2021-21642","kev_date_added":null,"published":"2021-04-21"},{"cvss_score":8.1,"headline":"CSRF vulnerability in Config File Provider Plugin","id":"CVE-2018-1000414","kev_date_added":null,"published":"2019-01-09"},{"cvss_score":7.5,"headline":"Jenkins Config File Provider Plugin improper credential masking vulnerability","id":"CVE-2023-40339","kev_date_added":null,"published":"2023-08-16"},{"cvss_score":6.5,"headline":"Incorrect permission checks in Jenkins Config File Provider Plugin allow enumerating credentials IDs","id":"CVE-2021-21643","kev_date_added":null,"published":"2021-04-21"},{"cvss_score":5.4,"headline":"CSRF vulnerability in Jenkins Config File Provider Plugin allows deleting configuration files","id":"CVE-2021-21644","kev_date_added":null,"published":"2021-04-21"},{"cvss_score":5.4,"headline":"Stored XSS vulnerability in Config File Provider Plugin","id":"CVE-2018-1000413","kev_date_added":null,"published":"2019-01-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Users with read-only access could view sensitive configuration files containing secrets due to missing authorization checks in the Config File Provider Plugin.","url":"https://insights.sbomify.com/CVE-2017-1000104/"}