{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2009-0318 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2009-0318 is a medium-severity path traversal vulnerability in n/a, published on 28 Jan 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2009-0318 and fix it if it is affected.\n\nWhat it is: CVE-2009-0318 is a medium-severity path traversal vulnerability in n/a, published on 28 Jan 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2009-0318 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-0318/ (Markdown: https://insights.sbomify.com/CVE-2009-0318/index.md)","id":"CVE-2009-0318","markdown":"https://insights.sbomify.com/CVE-2009-0318/index.md","name":"CVE-2009-0318","record":{"aliases":["DEBIAN-CVE-2009-0318","DTSA-190-1","GHSA-9cr7-r39p-2mx5"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Gnumeric spreadsheet","requires_auth":"none","summary":"Local attackers can execute arbitrary code by placing a malicious Python file in the current working directory when Gnumeric is launched.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gnumeric","vendor":"gnome"}],"cvss":{"score":6.9,"severity":"medium","source":"nvd","vector":"AV:L/AC:M/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Untrusted search path vulnerability in the GObject Python interpreter wrapper in Gnumeric allows local users to execute arbitrary code via a Trojan horse Python file in the current working directory, related to a vulnerability in the PySys_SetArgv function (CVE-2008-5983).","ecosystems":[],"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":"Path traversal in n/a","id":"CVE-2009-0318","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2009"},"n_packages":0,"n_references":9,"next":{"headline":"Denial of service in n/a","id":"CVE-2009-0319"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2009-0317"},"products":["n/a"],"published":"2009-01-28","related":[{"cvss_score":9.3,"headline":"Integer overflow in n/a","id":"CVE-2008-0668","kev_date_added":null,"published":"2008-02-11"},{"cvss_score":4.3,"headline":"Memory corruption in n/a","id":"CVE-2013-6836","kev_date_added":null,"published":"2013-12-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-07","vendors":["n/a"]},"summary":"Local attackers can execute arbitrary code by placing a malicious Python file in the current working directory when Gnumeric is launched.","url":"https://insights.sbomify.com/CVE-2009-0318/"}