Enclave memory disclosure via mutable output pointer
Published Jun 8, 2021 · Updated Sep 17, 2024
Memory disclosure in Google Asylo 0.6.2 and earlier allows local users to read trusted enclave memory through an untrusted call. TrustedPrimitives::UntrustedCall validates sgx_params->output while it resides in untrusted memory, then reads that field again for deserialization, allowing the pointer to change after validation. A local low-privileged attacker must win this check-to-use race; successful exploitation discloses arbitrary trusted enclave memory through the altered output pointer.
Summary
What happened
Memory disclosure in Google Asylo 0.6.2 and earlier allows local users to read trusted enclave memory through an untrusted call. TrustedPrimitives::UntrustedCall validates sgx_params->output while it resides in untrusted memory, then reads that field again for deserialization, allowing the pointer to change after validation. A local low-privileged attacker must win this check-to-use race; successful exploitation discloses arbitrary trusted enclave memory through the altered output pointer.
The record
- CVE
- CVE-2021-22548
- Published
- Jun 8, 2021
- Updated
- Sep 17, 2024
- Vendor
- Product
- Asylo
- Classifications
- CWE-788
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 8, 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.
Weakness, pattern, technique
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