CVE-2020-8904 Arbitrary trusted memory overwrite vulnerability in Asylo
Attackers can overwrite arbitrary trusted memory in Asylo enclaves due to missing pointer validation, 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-8904?
CVE-2020-8904 is a medium-severity memory corruption vulnerability in Google LLC Asylo, published on 12 Aug 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 the trusted memory of Asylo exists in versions prior to 0.6.0. As the ecall_restore function fails to validate the range of the output_len pointer, an attacker can manipulate the tmp_output_len value and write to an arbitrary location in the trusted (enclave) memory. We recommend updating Asylo to version 0.6.0 or later.
Which versions are affected by CVE-2020-8904?
It affects 1 product.
Products include Google Asylo.
How do I fix CVE-2020-8904?
No fix has been published for CVE-2020-8904 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-8904 being exploited?
There is no known exploitation of CVE-2020-8904 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-2021-22552 Memory overread secure enclave in Asylo 0.6.2
- CVE-2020-8935 Memory corruption in Asylo
Sources
Also known as GHSA-pc43-829f-g5gr.