{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10458 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-10458 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-10458 is a critical code injection vulnerability in Jenkins Puppet Enterprise Pipeline, published on 16 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10458 and fix it if it is affected.\n\nWhat it is: CVE-2019-10458 is a critical code injection vulnerability in Jenkins Puppet Enterprise Pipeline, published on 16 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10458 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline (Maven): affected all versions up to 1.3.1; no fix listed\n- org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline (Maven): affected all versions up to 1.3.1; 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-2019-10458/ (Markdown: https://insights.sbomify.com/CVE-2019-10458/index.md)","id":"CVE-2019-10458","markdown":"https://insights.sbomify.com/CVE-2019-10458/index.md","name":"CVE-2019-10458","record":{"aliases":["GHSA-mj9c-vjp9-pggh"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins plugin","requires_auth":"low_privilege","summary":"Attackers with script execution rights can bypass security restrictions to run arbitrary code via unsafe whitelist values in the Jenkins Puppet Enterprise Pipeline plugin.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"puppet_enterprise_pipeline","vendor":"jenkins"}],"cvss":{"score":9.9,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"Jenkins Puppet Enterprise Pipeline 1.3.1 and earlier specifies unsafe values in its custom Script Security whitelist, allowing attackers able to execute Script Security protected scripts to execute arbitrary code.","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":"Incorrect Authorization in Puppet Enterprise Pipeline Jenkins Plugin","id":"CVE-2019-10458","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Jenkins Mattermost Notification Plugin contains unencrypted storage of secret token","id":"CVE-2019-10459"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.3.1"],"package":"org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline","purl":null,"source":"GHSA-mj9c-vjp9-pggh"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["1.3.1"],"package":"org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline","purl":"pkg:maven/org.jenkins-ci.plugins.workflow/puppet-enterprise-pipeline","source":"GHSA-mj9c-vjp9-pggh"}],"prev":{"headline":"Missing permission check in Jenkins Oracle Cloud Infrastructure Compute Classic Plugin","id":"CVE-2019-10457"},"products":["Jenkins Puppet Enterprise Pipeline"],"published":"2019-10-16","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Jenkins project"]},"summary":"Attackers with script execution rights can bypass security restrictions to run arbitrary code via unsafe whitelist values in the Jenkins Puppet Enterprise Pipeline plugin.","url":"https://insights.sbomify.com/CVE-2019-10458/"}