Unchecked buffer overrun in ecall_restore

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• google asyloup to 0.6.0 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Google). Independent of NVD's CPE analysis and usually ahead of it.

• Google LLC Asylo

  • unspecified and later · up to and including 0.6.0affected

Other highest-scoring records for the same primary product.

• CVE-2020-8904Arbitrary trusted memory overwrite vulnerability in Asylo
  38Monitor
• CVE-2021-22550Enclave memory overwrite/overread vulnerability in Asylo UntrustedCacheMalloc::GetBuffer
  31Monitor
• CVE-2021-22549Arbitrary enclave memory overwrite vulnerability in Asylo TrustedPrimitives::UntrustedCall
  31Monitor
• CVE-2021-22548Arbitrary enclave memory overread vulnerability in Asylo TrustedPrimitives::UntrustedCall
  31Monitor
• CVE-2020-8935An arbitrary memory overwrite vulnerability in Asylo versions up to 0.6.0 allow an attacker to make an Ecall_restore function call to reallo
  31Monitor
• CVE-2020-8905Confidential Information Disclosure vulnerability in Asylo
  26Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1char buf[256];2memcpy(buf, pkt->data, pkt->len);

1char buf[256];2if (pkt->len > sizeof(buf)) {3  return -EINVAL;4}5memcpy(buf, pkt->data, pkt->len);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.