CVE-2020-8904

Arbitrary trusted memory overwrite vulnerability in Asylo

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.

Categories

6.4
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.06%
Third-Party Advisory github.com
Affected: Google LLC Asylo
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2020-8904?
CVE-2020-8904 has been scored as a medium severity vulnerability.
How to fix CVE-2020-8904?
To fix CVE-2020-8904, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-8904 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-8904 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-8904?
CVE-2020-8904 affects Google LLC Asylo.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.