{"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-2018-16831 in the wild and no public exploit code.","fix":"Upgrade smarty/smarty to 3.1.33 or later.","what":"CVE-2018-16831 is a medium-severity path traversal vulnerability in n/a, published on 11 Sep 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-2018-16831 and fix it if it is affected.\n\nWhat it is: CVE-2018-16831 is a medium-severity path traversal vulnerability in n/a, published on 11 Sep 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-2018-16831 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- smarty/smarty (Packagist): affected all versions; fixed in 3.1.33\n- smarty/smarty (Packagist): affected all versions; fixed in 3.1.33\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-2018-16831/ (Markdown: https://insights.sbomify.com/CVE-2018-16831/index.md)","id":"CVE-2018-16831","markdown":"https://insights.sbomify.com/CVE-2018-16831/index.md","name":"CVE-2018-16831","record":{"aliases":["DEBIAN-CVE-2018-16831","GHSA-65j5-vpm7-6xp4","UBUNTU-CVE-2018-16831"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Smarty template engine","requires_auth":"none","summary":"Attackers can bypass trusted directory restrictions in Smarty to read arbitrary files via path traversal in include statements.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smarty","vendor":"smarty"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Smarty before 3.1.33-dev-4 allows attackers to bypass the trusted_dir protection mechanism via a file:./../ substring in an include statement.","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 Path Traversal Vulnerability","id":"CVE-2018-16831","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"path_traversal","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2018-16832"},"packages":[{"ecosystem":"Packagist","fixed":["3.1.33"],"introduced":["0"],"last_affected":[],"package":"smarty/smarty","purl":null,"source":"GHSA-65j5-vpm7-6xp4"},{"ecosystem":"Packagist","fixed":["3.1.33"],"introduced":["0"],"last_affected":[],"package":"smarty/smarty","purl":"pkg:composer/smarty/smarty","source":"GHSA-65j5-vpm7-6xp4"}],"prev":{"headline":"SQL injection in n/a","id":"CVE-2018-16822"},"products":["n/a"],"published":"2018-09-11","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 bypass trusted directory restrictions in Smarty to read arbitrary files via path traversal in include statements.","url":"https://insights.sbomify.com/CVE-2018-16831/"}