{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-7157 exists.","fix":"No fix has been published for CVE-2006-7157 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-7157 is a high-severity memory corruption vulnerability in n/a, published on 7 Mar 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2006-7157 and fix it if it is affected.\n\nWhat it is: CVE-2006-7157 is a high-severity memory corruption vulnerability in n/a, published on 7 Mar 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-7157 exists.\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-2006-7157/ (Markdown: https://insights.sbomify.com/CVE-2006-7157/index.md)","id":"CVE-2006-7157","markdown":"https://insights.sbomify.com/CVE-2006-7157/index.md","name":"CVE-2006-7157","record":{"aliases":["GHSA-2j79-8rwp-pjrp"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Google Earth","requires_auth":"none","summary":"Remote attackers can crash Google Earth by tricking users into opening a malicious KML or KMZ file with a long href element.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"earth","vendor":"google"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"AV:N/AC:M/Au:N/C:N/I:N/A:C","version":"2.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Buffer overflow in Google Earth v4.0.2091 (beta) allows remote user-assisted attackers to cause a denial of service (crash) via a KML or KMZ file with a long href element.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-09-14","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-09-14","kind":"exploitdb","ref":"28785","stars":null,"title":"Google Earth 4.0.2091 (Beta) - '.KML'/'.KMZ' Buffer Overflow"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2006-7157","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2006"},"n_packages":0,"n_references":6,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-7158"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2006-7156"},"products":["n/a"],"published":"2007-03-07","related":[{"cvss_score":9.3,"headline":"Path traversal in n/a","id":"CVE-2010-3134","kev_date_added":null,"published":"2010-08-26"},{"cvss_score":7.8,"headline":"DLL Hijacking in Google Earth Pro Windows installer","id":"CVE-2020-8895","kev_date_added":null,"published":"2020-04-21"},{"cvss_score":4.2,"headline":"Buffer Overflow in Google Earth Pro","id":"CVE-2020-8896","kev_date_added":null,"published":"2020-05-04"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can crash Google Earth by tricking users into opening a malicious KML or KMZ file with a long href element.","url":"https://insights.sbomify.com/CVE-2006-7157/"}