CVE-2020-8937 Arbitrary enclave memory location write from untrusted environment

Medium 5.3 Published Updated

An attacker can write arbitrary memory within the enclave via an unvalidated pointer in Asylo, potentially leading to code execution or privilege escalation.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is CVE-2020-8937?

CVE-2020-8937 is a medium-severity memory corruption vulnerability in Google LLC Asylo, published on 15 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

An arbitrary memory overwrite vulnerability in Asylo versions up to 0.6.0 allows an attacker to make a host call to enc_untrusted_create_wait_queue that uses a pointer queue that relies on UntrustedLocalMemcpy, which fails to validate where the pointer is located. This allows an attacker to write memory values from within the enclave. We recommend upgrading past commit a37fb6a0e7daf30134dbbf357c9a518a1026aa02

Weakness: CWE-787, CWE-120

Which versions are affected by CVE-2020-8937?

It affects 1 product.

Products include Google Asylo.

How do I fix CVE-2020-8937?

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

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2020-8937 being exploited?

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

Sources

Also known as GHSA-wv62-pfmm-x787.

Is CVE-2020-8937 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free