# CVE-2006-7157: Memory corruption in n/a

> Remote attackers can crash Google Earth by tricking users into opening a malicious KML or KMZ file with a long href element.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2j79-8rwp-pjrp

## What is CVE-2006-7157?

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.

### Official 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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2006-7157?

It affects 1 product.


Products: Google Earth.

## How do I fix CVE-2006-7157?

No fix has been published for CVE-2006-7157 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-7157 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-7157 exists.

Public exploit code:

- Google Earth 4.0.2091 (Beta) - '.KML'/'.KMZ' Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-3134](https://insights.sbomify.com/CVE-2010-3134/): Path traversal in n/a (critical 9.3)
- [CVE-2020-8895](https://insights.sbomify.com/CVE-2020-8895/): DLL Hijacking in Google Earth Pro Windows installer (high 7.8)
- [CVE-2020-8896](https://insights.sbomify.com/CVE-2020-8896/): Buffer Overflow in Google Earth Pro (medium 4.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7157 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-7157 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-7157/ (Markdown: https://insights.sbomify.com/CVE-2006-7157/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-7157
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-7157
- OSV: https://osv.dev/vulnerability/CVE-2006-7157

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-7157/
Summaries are generated and may contain mistakes; the official description above is the record.