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.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
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.
Which versions are affected by CVE-2020-8935?
It affects 1 product.
Products include 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.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
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 Arbitrary enclave memory overread vulnerability in Asylo TrustedPrimitives::UntrustedCall
- CVE-2021-22549 Arbitrary enclave memory overwrite vulnerability in Asylo TrustedPrimitives::UntrustedCall
- CVE-2021-22550 Enclave memory overwrite/overread vulnerability in Asylo UntrustedCacheMalloc::GetBuffer
- CVE-2020-8904 Arbitrary trusted memory overwrite vulnerability in Asylo
- CVE-2021-22552 Memory overread secure enclave in Asylo 0.6.2
Sources
Also known as GHSA-6g37-4jmq-qq2x.