Privilege escalation via poisoned floating-point control state
Published Feb 13, 2020 · Updated Aug 4, 2024
Improper initialization in Intel Software Guard Extensions SDK allows local users to alter enclave floating-point computations. The enclave-entry runtime fails to sanitize inherited x87 FPU and SSE control state, allowing hostile rounding, precision, or exception settings to affect enclave calculations. A local low-privilege user must prime that state before entry; affected floating-point enclaves can then produce attacker-influenced results.
Summary
What happened
Improper initialization in Intel Software Guard Extensions SDK allows local users to alter enclave floating-point computations. The enclave-entry runtime fails to sanitize inherited x87 FPU and SSE control state, allowing hostile rounding, precision, or exception settings to affect enclave calculations. A local low-privilege user must prime that state before entry; affected floating-point enclaves can then produce attacker-influenced results.
The record
- CVE
- CVE-2020-0561
- Published
- Feb 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Intel Corporation
- Product
- Intel Software Guard Extensions SDK
- Classifications
- CWE-665, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 13, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=before v2.6.100.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
- Faulty Point Unit proof-of-concept exploitsproof of concept · 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