{"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-2009-5054 in the wild and no public exploit code.","fix":"Upgrade smarty/smarty to 3.0.0-beta4 or later.","what":"CVE-2009-5054 is a high-severity vulnerability in n/a, published on 3 Feb 2011. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-5054 and fix it if it is affected.\n\nWhat it is: CVE-2009-5054 is a high-severity vulnerability in n/a, published on 3 Feb 2011. 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-2009-5054 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- smarty/smarty (Packagist): affected all versions; fixed in 3.0.0-beta4\n- smarty/smarty (Packagist): affected all versions; fixed in 3.0.0-beta4\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-2009-5054/ (Markdown: https://insights.sbomify.com/CVE-2009-5054/index.md)","id":"CVE-2009-5054","markdown":"https://insights.sbomify.com/CVE-2009-5054/index.md","name":"CVE-2009-5054","record":{"aliases":["DEBIAN-CVE-2009-5054","GHSA-6m9f-8vwq-97pm"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP template engine","requires_auth":"none","summary":"Smarty library fails to respect umask settings, allowing attackers to bypass intended file access restrictions via standard filesystem operations.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smarty","vendor":"smarty"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Smarty before 3.0.0 beta 4 does not consider the umask value when setting the permissions of files, which might allow attackers to bypass intended access restrictions via standard filesystem operations.","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 Does Not Consider Umask Values When Setting Permissions","id":"CVE-2009-5054","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"misconfiguration","year":"2009"},"n_packages":2,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2009-5055"},"packages":[{"ecosystem":"Packagist","fixed":["3.0.0-beta4"],"introduced":["0"],"last_affected":[],"package":"smarty/smarty","purl":null,"source":"GHSA-6m9f-8vwq-97pm"},{"ecosystem":"Packagist","fixed":["3.0.0-beta4"],"introduced":["0"],"last_affected":[],"package":"smarty/smarty","purl":"pkg:composer/smarty/smarty","source":"GHSA-6m9f-8vwq-97pm"}],"prev":{"headline":"Code injection in n/a","id":"CVE-2009-5053"},"products":["n/a"],"published":"2011-02-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-09-17","vendors":["n/a"]},"summary":"Smarty library fails to respect umask settings, allowing attackers to bypass intended file access restrictions via standard filesystem operations.","url":"https://insights.sbomify.com/CVE-2009-5054/"}