Arbitrary enclave memory location write from untrusted environment

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

cvss: 5.3; 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 2%
public exploits: 0; none known

An arbitrary memory overwrite vulnerability in Asylo versions up to 0.6.0 allows an attacker to make a host call to FromkLinuxSockAddr with attacker controlled content and size of klinux_addr which allows an attacker to write memory values from within the enclave. We recommend upgrading past commit a37fb6a0e7daf30134dbbf357c9a518a1026aa02

Patch / fix

links 1

github.com/google/asylo@bda9772 commit

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

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	3.3	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/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-787 Out-of-bounds Write

References

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

Sources

CVE List CVE-2020-8938
NVD CVE-2020-8938

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.