{"answers":{"affected":"2 open source packages ship an affected version, including cprice404:pipeline-classpath. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2650 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2650 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2650 is a high-severity vulnerability in Pipeline: Classpath Step Jenkins plugin, published on 27 Jul 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-2650 and fix it if it is affected.\n\nWhat it is: CVE-2017-2650 is a high-severity vulnerability in Pipeline: Classpath Step Jenkins plugin, published on 27 Jul 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-2650 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- cprice404:pipeline-classpath (Maven): affected all versions; no fix listed\n- cprice404:pipeline-classpath (Maven): affected all versions; no fix listed\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-2650/ (Markdown: https://insights.sbomify.com/CVE-2017-2650/index.md)","id":"CVE-2017-2650","markdown":"https://insights.sbomify.com/CVE-2017-2650/index.md","name":"CVE-2017-2650","record":{"aliases":["GHSA-r5c7-qcc9-5v7m"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Attackers with SCM or configure permissions can bypass the Script Security sandbox to execute arbitrary code.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"pipeline_classpath_step","vendor":"jenkins"}],"cvss":{"score":8.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-592","name":"DEPRECATED: Authentication Bypass Issues"}],"description":"It was found that the use of Pipeline: Classpath Step Jenkins plugin enables a bypass of the Script Security sandbox for users with SCM commit access, as well as users with e.g. Job/Configure permission in Jenkins.","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":false,"headline":"Jenkins Pipeline Classpath Step plugin allowed Script Security sandbox bypass","id":"CVE-2017-2650","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":2,"n_references":2,"next":{"headline":"Exposure of Sensitive Information to an Unauthorized Actor in Jenkins-mailer-plugin","id":"CVE-2017-2651"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":[],"last_affected":[],"package":"cprice404:pipeline-classpath","purl":null,"source":"GHSA-r5c7-qcc9-5v7m"},{"ecosystem":"Maven","fixed":[],"introduced":[],"last_affected":[],"package":"cprice404:pipeline-classpath","purl":"pkg:maven/cprice404/pipeline-classpath","source":"GHSA-r5c7-qcc9-5v7m"}],"prev":{"headline":"Jenkins Active Directory Plugin did not verify certificate of AD server","id":"CVE-2017-2649"},"products":["Pipeline: Classpath Step Jenkins plugin"],"published":"2018-07-27","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":["Jenkins project"]},"summary":"Attackers with SCM or configure permissions can bypass the Script Security sandbox to execute arbitrary code.","url":"https://insights.sbomify.com/CVE-2017-2650/"}