# CVE-2020-8896: Buffer Overflow in Google Earth Pro

> A buffer overflow in Google Earth Pro allows attackers to read sensitive data via a Man-in-the-Middle attack using a crafted key.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-33rh-fh49-758p

## What is CVE-2020-8896?

CVE-2020-8896 is a medium-severity memory corruption vulnerability in Google Earth Pro, published on 4 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Buffer Overflow vulnerability in the khcrypt implementation in Google Earth Pro versions up to and including 7.3.2 allows an attacker to perform a Man-in-the-Middle attack using a specially crafted key to read data past the end of the buffer used to hold it. Mitigation: Update to Google Earth Pro 7.3.3.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2020-8896?

It affects 1 product.


Products: Google Earth.

## How do I fix CVE-2020-8896?

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

## Is CVE-2020-8896 being exploited?

There is no known exploitation of CVE-2020-8896 in the wild and no public exploit code.

## Other vulnerabilities in Google Earth Pro

- [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-2006-7157](https://insights.sbomify.com/CVE-2006-7157/): Memory corruption in n/a (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-8896 and fix it if it is affected.

What it is: CVE-2020-8896 is a medium-severity memory corruption vulnerability in Google Earth Pro, published on 4 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-8896 in the wild and no public exploit code.

Affected product: Google Earth Pro. 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-2020-8896/ (Markdown: https://insights.sbomify.com/CVE-2020-8896/index.md)
```

## Sources

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

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