Enclave memory disclosure via unchecked syscall response
Published Aug 2, 2021 · Updated Sep 17, 2024
Buffer over-read in Google Asylo 0.6.2 and earlier allows local users to read secure-enclave memory through a crafted syscall response. enc_untrusted_syscall builds a MessageReader over the host-supplied response and previously called Validate without confirming that response_reader.sysno() matched the requested syscall number. A local user able to alter the untrusted host response can bypass the intended validation and disclose enclave memory; no network path is reported.
Summary
What happened
Buffer over-read in Google Asylo 0.6.2 and earlier allows local users to read secure-enclave memory through a crafted syscall response. enc_untrusted_syscall builds a MessageReader over the host-supplied response and previously called Validate without confirming that response_reader.sysno() matched the requested syscall number. A local user able to alter the untrusted host response can bypass the intended validation and disclose enclave memory; no network path is reported.
The record
- CVE
- CVE-2021-22552
- Published
- Aug 2, 2021
- Updated
- Sep 17, 2024
- Vendor
- Product
- Asylo
- Classifications
- CWE-125, CWE-126
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 2, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=0.6.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo