{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:ec2. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000502 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:ec2 to 1.38 or later.","what":"CVE-2017-1000502 is a high-severity command injection vulnerability in n/a, published on 24 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1000502 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000502 is a high-severity command injection vulnerability in n/a, published on 24 Jan 2018. 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-1000502 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:ec2 (Maven): affected all versions; fixed in 1.38\n- org.jenkins-ci.plugins:ec2 (Maven): affected all versions; fixed in 1.38\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-1000502/ (Markdown: https://insights.sbomify.com/CVE-2017-1000502/index.md)","id":"CVE-2017-1000502","markdown":"https://insights.sbomify.com/CVE-2017-1000502/index.md","name":"CVE-2017-1000502","record":{"aliases":["GHSA-wp79-cpv2-9g7m"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins CI server","requires_auth":"low_privilege","summary":"Users with agent configuration permissions can execute arbitrary shell commands on the Jenkins master node by configuring EC2 agents.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ec2","vendor":"jenkins"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Users with permission to create or configure agents in Jenkins 1.37 and earlier could configure an EC2 agent to run arbitrary shell commands on the master node whenever the agent was supposed to be launched. Configuration of these agents now requires the 'Run Scripts' permission typically only granted to administrators.","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":"Arbitrary shell command execution in Jenkins EC2 Plugin","id":"CVE-2017-1000502","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"command_injection","year":"2017"},"n_packages":2,"n_references":1,"next":{"headline":"Race Condition in Jenkins","id":"CVE-2017-1000503"},"packages":[{"ecosystem":"Maven","fixed":["1.38"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:ec2","purl":null,"source":"GHSA-wp79-cpv2-9g7m"},{"ecosystem":"Maven","fixed":["1.38"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:ec2","purl":"pkg:maven/org.jenkins-ci.plugins/ec2","source":"GHSA-wp79-cpv2-9g7m"}],"prev":{"headline":"Path traversal in n/a","id":"CVE-2017-1000501"},"products":["n/a"],"published":"2018-01-24","related":[{"cvss_score":5.5,"headline":"Jenkins Amazon EC2 Plugin leaked beginning of private key in system log","id":"CVE-2019-10364","kev_date_added":null,"published":"2019-07-31"}],"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-16","vendors":["n/a"]},"summary":"Users with agent configuration permissions can execute arbitrary shell commands on the Jenkins master node by configuring EC2 agents.","url":"https://insights.sbomify.com/CVE-2017-1000502/"}