{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:deploy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000113 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:deploy to 1.13 or later.","what":"CVE-2017-1000113 is a medium-severity vulnerability in n/a, published on 4 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1000113 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000113 is a medium-severity vulnerability in n/a, published on 4 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-1000113 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:deploy (Maven): affected all versions; fixed in 1.13\n- org.jenkins-ci.plugins:deploy (Maven): affected all versions; fixed in 1.13\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-1000113/ (Markdown: https://insights.sbomify.com/CVE-2017-1000113/index.md)","id":"CVE-2017-1000113","markdown":"https://insights.sbomify.com/CVE-2017-1000113/index.md","name":"CVE-2017-1000113","record":{"aliases":["GHSA-3q6p-r6rr-266x"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"The Deploy to container Plugin stored passwords unencrypted, allowing local or extended-read users to retrieve sensitive credentials.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"deploy","vendor":"jenkins"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/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":"The Deploy to container Plugin stored passwords unencrypted as part of its configuration. This allowed users with Jenkins master local file system access, or users with Extended Read access to the jobs it is used in, to retrieve those passwords. The Deploy to container Plugin now integrates with Credentials Plugin to store passwords securely, and automatically migrates existing passwords.","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 Deploy to container Plugin stored plain text passwords in job configuration","id":"CVE-2017-1000113","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":"Exposure of Sensitive Information in Jenkins Datadog plugin","id":"CVE-2017-1000114"},"packages":[{"ecosystem":"Maven","fixed":["1.13"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:deploy","purl":null,"source":"GHSA-3q6p-r6rr-266x"},{"ecosystem":"Maven","fixed":["1.13"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:deploy","purl":"pkg:maven/org.jenkins-ci.plugins/deploy","source":"GHSA-3q6p-r6rr-266x"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-1000112"},"products":["n/a"],"published":"2017-10-04","related":[],"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":"The Deploy to container Plugin stored passwords unencrypted, allowing local or extended-read users to retrieve sensitive credentials.","url":"https://insights.sbomify.com/CVE-2017-1000113/"}