# CVE-2021-22548: Arbitrary enclave memory overread vulnerability in Asylo TrustedPrimitives::UntrustedCall

> An attacker can read trusted memory regions by manipulating untrusted pointers in Asylo, leading to sensitive data disclosure.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2021
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-j42g-3m6p-674j

## What is CVE-2021-22548?

CVE-2021-22548 is a medium-severity vulnerability in Google LLC Asylo, published on 8 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An attacker can change the pointer to untrusted memory to point to trusted memory region which causes copying trusted memory to trusted memory, if the latter is later copied out, it allows for reading of memory regions from the trusted region. It is recommended to update past 0.6.2 or git commit https://github.com/google/asylo/commit/53ed5d8fd8118ced1466e509606dd2f473707a5c

Weakness: CWE-788 (Access of Memory Location After End of Buffer)

## Which versions are affected by CVE-2021-22548?

It affects 1 product.


Products: Google Asylo.

## How do I fix CVE-2021-22548?

No fix has been published for CVE-2021-22548 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-22548 being exploited?

There is no known exploitation of CVE-2021-22548 in the wild and no public exploit code.

## Other vulnerabilities in Google LLC Asylo

- [CVE-2021-22549](https://insights.sbomify.com/CVE-2021-22549/): Arbitrary enclave memory overwrite vulnerability in Asylo TrustedPrimitives::UntrustedCall (medium 6.5)
- [CVE-2021-22550](https://insights.sbomify.com/CVE-2021-22550/): Enclave memory overwrite/overread vulnerability in Asylo UntrustedCacheMalloc::GetBuffer (medium 6.5)
- [CVE-2020-8904](https://insights.sbomify.com/CVE-2020-8904/): Arbitrary trusted memory overwrite vulnerability in Asylo (medium 6.4)
- [CVE-2021-22552](https://insights.sbomify.com/CVE-2021-22552/): Memory overread secure enclave in Asylo 0.6.2 (medium 5.3)
- [CVE-2020-8935](https://insights.sbomify.com/CVE-2020-8935/): Memory corruption in Asylo (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22548 and fix it if it is affected.

What it is: CVE-2021-22548 is a medium-severity vulnerability in Google LLC Asylo, published on 8 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22548 in the wild and no public exploit code.

Affected product: Google LLC Asylo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-22548/ (Markdown: https://insights.sbomify.com/CVE-2021-22548/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-22548
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-22548
- OSV: https://osv.dev/vulnerability/CVE-2021-22548

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-22548/
Summaries are generated and may contain mistakes; the official description above is the record.