# CVE-2020-8935: Memory corruption in Asylo

> An arbitrary memory overwrite in Asylo allows attackers to corrupt enclave memory via Ecall_restore, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6g37-4jmq-qq2x

## What is CVE-2020-8935?

CVE-2020-8935 is a medium-severity memory corruption vulnerability in Google LLC Asylo, published on 15 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An arbitrary memory overwrite vulnerability in Asylo versions up to 0.6.0 allow an attacker to make an Ecall_restore function call to reallocate untrusted code and overwrite sections of the Enclave memory address. We recommend updating your library.

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Google Asylo.

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

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

## Is CVE-2020-8935 being exploited?

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

## Other vulnerabilities in Google LLC Asylo

- [CVE-2021-22548](https://insights.sbomify.com/CVE-2021-22548/): Arbitrary enclave memory overread vulnerability in Asylo TrustedPrimitives::UntrustedCall (medium 6.5)
- [CVE-2021-22549](https://insights.sbomify.com/CVE-2021-22549/): Arbitrary enclave memory overwrite vulnerability in Asylo TrustedPrimitives::UntrustedCall (medium 6.5)
- [CVE-2021-22550](https://insights.sbomify.com/CVE-2021-22550/): Enclave memory overwrite/overread vulnerability in Asylo UntrustedCacheMalloc::GetBuffer (medium 6.5)
- [CVE-2020-8904](https://insights.sbomify.com/CVE-2020-8904/): Arbitrary trusted memory overwrite vulnerability in Asylo (medium 6.4)
- [CVE-2021-22552](https://insights.sbomify.com/CVE-2021-22552/): Memory overread secure enclave in Asylo 0.6.2 (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8935 is a medium-severity memory corruption vulnerability in Google LLC Asylo, published on 15 Dec 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-8935 in the wild and no public exploit code.

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

## Sources

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

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