{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2012-5138 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2012-5138 is a critical path traversal vulnerability in Google Chrome, published on 4 Dec 2012. It can be exploited over the network."},"fix_prompt":"Check this codebase for CVE-2012-5138 and fix it if it is affected.\n\nWhat it is: CVE-2012-5138 is a critical path traversal vulnerability in Google Chrome, published on 4 Dec 2012. It can be exploited over the network.\nExploitation: There is no known exploitation of CVE-2012-5138 in the wild and no public exploit code.\n\nAffected product: Google Chrome. 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-2012-5138/ (Markdown: https://insights.sbomify.com/CVE-2012-5138/index.md)","id":"CVE-2012-5138","markdown":"https://insights.sbomify.com/CVE-2012-5138/index.md","name":"CVE-2012-5138","record":{"aliases":["GHSA-fmp2-5mxc-mvcf"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Google Chrome browser","requires_auth":"unknown","summary":"Google Chrome fails to properly handle file paths, potentially allowing attackers to access or manipulate files via unspecified vectors.","user_interaction":"unknown","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Chrome","cpe":[{"product":"chrome","vendor":"google"},{"product":"opensuse","vendor":"opensuse"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Google Chrome before 23.0.1271.95 does not properly handle file paths, which has unspecified impact and attack vectors.","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-2012-5138","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:chrome","products":["google:chrome","opensuse:opensuse"],"type":"path_traversal","year":"2012"},"n_packages":0,"n_references":6,"next":{"headline":"Use after free in n/a","id":"CVE-2012-5139"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2012-5137"},"products":["n/a"],"published":"2012-12-04","related":[{"cvss_score":9.6,"headline":"Google Chromium GPU Heap Buffer Overflow","id":"CVE-2022-4135","kev_date_added":"2022-11-28","published":"2022-11-25"},{"cvss_score":9.6,"headline":"Google Chrome Use-After-Free","id":"CVE-2020-16017","kev_date_added":"2021-11-03","published":"2021-01-08"},{"cvss_score":9.6,"headline":"Google Chrome for Android UI Heap Buffer Overflow","id":"CVE-2020-16010","kev_date_added":"2021-11-03","published":"2020-11-03"},{"cvss_score":8.8,"headline":"Google Chromium V8 Out of Bounds Write","id":"CVE-2026-87491","kev_date_added":"2026-09-09","published":"2026-09-09"},{"cvss_score":8.8,"headline":"Google Chromium V8 Type Confusion","id":"CVE-2026-85046","kev_date_added":"2026-09-04","published":"2026-09-03"},{"cvss_score":8.8,"headline":"Google Chromium V8 Out-of-Bounds Read and Write","id":"CVE-2026-11645","kev_date_added":"2026-06-09","published":"2026-06-08"},{"cvss_score":8.8,"headline":"Google Dawn Use-After-Free","id":"CVE-2026-5281","kev_date_added":"2026-04-01","published":"2026-04-01"}],"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-06","vendors":["n/a"]},"summary":"Google Chrome fails to properly handle file paths, potentially allowing attackers to access or manipulate files via unspecified vectors.","url":"https://insights.sbomify.com/CVE-2012-5138/"}