CVE-2020-8904
An arbitrary memory overwrite vulnerability in the trusted memory of Asylo exists in versions prior to 0.6.0.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.23%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.1
- 9.6 CRITICALCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H
- EPSS
- 0.23% probability · 14th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-823, CWE-119
- Affected
- google/asylo
- Source
- cve-coordination@google.com
EPSS 0.2% since 27 October 2026; no change recorded yet. Points are recorded when the score first appears and whenever it moves by a percentage point or more.
References
- https://github.com/google/asylo/commit/e582f36ac49ee11a21d23ad6a30c333092e0a94ePatch, Third Party Advisory
- https://github.com/google/asylo/commit/e582f36ac49ee11a21d23ad6a30c333092e0a94ePatch, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.