Local trusted-memory overwrite via unchecked pointer
Published Jun 8, 2021 · Updated Sep 17, 2024
Asylo before 0.6.2 allows local users to overwrite arbitrary trusted enclave memory through TrustedPrimitives::UntrustedCall. The function validates an untrusted input pointer and then uses the mutable pointer again, allowing it to be changed to trusted memory after the bounds check. The attack requires low-privilege local access to an Asylo enclave application and can compromise enclave confidentiality and integrity while causing limited availability impact.
Summary
What happened
Asylo before 0.6.2 allows local users to overwrite arbitrary trusted enclave memory through TrustedPrimitives::UntrustedCall. The function validates an untrusted input pointer and then uses the mutable pointer again, allowing it to be changed to trusted memory after the bounds check. The attack requires low-privilege local access to an Asylo enclave application and can compromise enclave confidentiality and integrity while causing limited availability impact.
The record
- CVE
- CVE-2021-22549
- Published
- Jun 8, 2021
- Updated
- Sep 17, 2024
- Vendor
- Product
- Asylo
- Classifications
- CWE-823, T1203
- 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