{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:docker-commons. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000094 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:docker-commons to 1.8 or later.","what":"CVE-2017-1000094 is a medium-severity 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-1000094 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000094 is a medium-severity 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-1000094 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:docker-commons (Maven): affected all versions; fixed in 1.8\n- org.jenkins-ci.plugins:docker-commons (Maven): affected all versions; fixed in 1.8\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-1000094/ (Markdown: https://insights.sbomify.com/CVE-2017-1000094/index.md)","id":"CVE-2017-1000094","markdown":"https://insights.sbomify.com/CVE-2017-1000094/index.md","name":"CVE-2017-1000094","record":{"aliases":["GHSA-69cj-g7mw-mh72"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Docker plugin","requires_auth":"low_privilege","summary":"Attackers with read access can list valid Docker credential IDs, potentially aiding credential theft via other vulnerabilities.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"docker_commons","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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Docker Commons Plugin provides a list of applicable credential IDs to allow users configuring a job to select the one they'd like to use to authenticate with a Docker Registry. This functionality did not check permissions, allowing any user with Overall/Read permission to get a list of valid credentials IDs. Those could be used as part of an attack to capture the credentials using another vulnerability.","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":"Jenkins Docker Commons Plugin allows any user with Overall/Read permission to get list of valid credentials IDs","id":"CVE-2017-1000094","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":2,"n_references":1,"next":{"headline":"Unsafe methods in the default list of approved signatures in Jenkins Script Security Plugin","id":"CVE-2017-1000095"},"packages":[{"ecosystem":"Maven","fixed":["1.8"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:docker-commons","purl":null,"source":"GHSA-69cj-g7mw-mh72"},{"ecosystem":"Maven","fixed":["1.8"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:docker-commons","purl":"pkg:maven/org.jenkins-ci.plugins/docker-commons","source":"GHSA-69cj-g7mw-mh72"}],"prev":{"headline":"Jenkins Poll SCM Plugin vulnerable to Cross-Site Request Forgery","id":"CVE-2017-1000093"},"products":["n/a"],"published":"2017-10-04","related":[{"cvss_score":8.8,"headline":"OS command execution vulnerability in Jenkins Docker Commons Plugin","id":"CVE-2022-20617","kev_date_added":null,"published":"2022-01-12"}],"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-08-05","vendors":["n/a"]},"summary":"Attackers with read access can list valid Docker credential IDs, potentially aiding credential theft via other vulnerabilities.","url":"https://insights.sbomify.com/CVE-2017-1000094/"}