Enclave code execution via exception reentry
Published Jul 14, 2021 · Updated Aug 10, 2026
Exception-handling reentrancy in Open Enclave SDK 0.1.1 through 0.17.0 allows local users to hijack enclave control flow. The SGX entry path permits an exception immediately after EENTER to return to a malicious host before RSP is initialized, then resumes the enclave on a host-controlled stack. Exploitation requires a host able to interrupt enclave execution and enables enclave-memory disclosure or return-oriented code execution.
Summary
What happened
Exception-handling reentrancy in Open Enclave SDK 0.1.1 through 0.17.0 allows local users to hijack enclave control flow. The SGX entry path permits an exception immediately after EENTER to return to a malicious host before RSP is initialized, then resumes the enclave on a host-controlled stack. Exploitation requires a host able to interrupt enclave execution and enables enclave-memory disclosure or return-oriented code execution.
The record
- CVE
- CVE-2021-33767
- Published
- Jul 14, 2021
- Updated
- Aug 10, 2026
- Vendor
- Open Enclave
- Product
- Open Enclave SDK
- Classifications
- T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jul 14, 2021CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record 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=0.1.1 <0.17.1
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
- SmashEx proof-of-concept exploitsfunctional · demonstrated
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