Arbitrary enclave memory overwrite vulnerability in Asylo TrustedPrimitives::UntrustedCall

published 2021-06-08 5y ago modified 2026-06-17 4mo ago also EUVD-2021-9690

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 1%
public exploits: 0; none known

An attacker can modify the address to point to trusted memory to overwrite arbitrary trusted memory. It is recommended to update past 0.6.2 or git commit https://github.com/google/asylo/commit/53ed5d8fd8118ced1466e509606dd2f473707a5c

Patch / fix

fixed in 1 links 1

google asylo 0.6.2

github.com/google/asylo@ecfcd00 commit

Is CVE-2021-22549 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.5	CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
NVD	3.1	7.8	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	4.6	AV:L/AC:L/Au:N/C:P/I:P/A:P

Affected products

Google LLC Asylo

Classification

Weakness

CWE-823 Use of Out-of-range Pointer Offset
CWE-668 Exposure of Resource to Wrong Sphere

References

github.com /google/asylo/commit/ecfcd0008b6f8f63c6fa3cc1b62fcd4a52f2c0ad
patch, third-party-advisory

Sources

CVE List CVE-2021-22549
NVD CVE-2021-22549

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.