{"answers":{"affected":"2 open source packages ship an affected version, including smarty/smarty. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000480 in the wild and no public exploit code.","fix":"Upgrade smarty/smarty to 3.1.32 or later.","what":"CVE-2017-1000480 is a critical code injection vulnerability in n/a, published on 3 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1000480 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000480 is a critical code injection vulnerability in n/a, published on 3 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-1000480 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- smarty/smarty (Packagist): affected from 3; fixed in 3.1.32\n- smarty/smarty (Packagist): affected from 3; fixed in 3.1.32\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-1000480/ (Markdown: https://insights.sbomify.com/CVE-2017-1000480/index.md)","id":"CVE-2017-1000480","markdown":"https://insights.sbomify.com/CVE-2017-1000480/index.md","name":"CVE-2017-1000480","record":{"aliases":["DEBIAN-CVE-2017-1000480","DLA-1249-1","DSA-4094-1","GHSA-9m49-vhwv-422g","MGASA-2018-0118","UBUNTU-CVE-2017-1000480"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP template engine","requires_auth":"none","summary":"Attackers can execute arbitrary PHP code via unsanitized template names in Smarty's fetch or display functions.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smarty","vendor":"smarty"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"Smarty 3 before 3.1.32 is vulnerable to a PHP code injection when calling fetch() or display() functions on custom resources that does not sanitize template name.","ecosystems":["Packagist"],"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":"Smarty PHP code injection","id":"CVE-2017-1000480","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"code_injection","year":"2017"},"n_packages":2,"n_references":4,"next":{"headline":"Products.CMFPlone Open Redirect Vulnerability","id":"CVE-2017-1000481"},"packages":[{"ecosystem":"Packagist","fixed":["3.1.32"],"introduced":["3"],"last_affected":[],"package":"smarty/smarty","purl":null,"source":"GHSA-9m49-vhwv-422g"},{"ecosystem":"Packagist","fixed":["3.1.32"],"introduced":["3"],"last_affected":[],"package":"smarty/smarty","purl":"pkg:composer/smarty/smarty","source":"GHSA-9m49-vhwv-422g"}],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2017-1000479"},"products":["n/a"],"published":"2018-01-03","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-5052","kev_date_added":null,"published":"2011-02-03"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2010-4722","kev_date_added":null,"published":"2011-02-03"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2010-4724","kev_date_added":null,"published":"2011-02-03"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2010-4725","kev_date_added":null,"published":"2011-02-03"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2010-4726","kev_date_added":null,"published":"2011-02-03"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2010-4727","kev_date_added":null,"published":"2011-02-03"},{"cvss_score":10,"headline":"Command injection in n/a","id":"CVE-2009-1669","kev_date_added":null,"published":"2009-05-18"}],"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 can execute arbitrary PHP code via unsanitized template names in Smarty's fetch or display functions.","url":"https://insights.sbomify.com/CVE-2017-1000480/"}