Unchecked buffer overrun in ecall_restore

published 2020-12-15 5y ago modified 2026-06-17 4mo ago also EUVD-2020-29775

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

An arbitrary memory write vulnerability in Asylo versions up to 0.6.0 allows an untrusted attacker to make a call to ecall_restore using the attribute output which fails to check the range of a pointer. An attacker can use this pointer to write to arbitrary memory addresses including those within the secure enclave We recommend upgrading past commit 382da2b8b09cbf928668a2445efb778f76bd9c8a

Is CVE-2020-8944 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.16% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

github.com https://github.com/google/asylo/commit/382da2b8b09cbf928668a2445efb778f76bd9c8a referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

Google LLC Asylo

Classification

Weakness

CWE-120 Buffer Copy without Checking Size of Input
CWE-787 Out-of-bounds Write

References

github.com /google/asylo/commit/382da2b8b09cbf928668a2445efb778f76bd9c8a
exploit, third-party-advisory

Sources

CVE List CVE-2020-8944
NVD CVE-2020-8944

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.