Cited by 319Security and Verification in ComputingCryptographic Implementations and SecurityCryptography and Data Security

SgxPectre: Stealing Intel Secrets from SGX Enclaves Via Speculative Execution

Open access
Chen, Guoxing, Chen, Sanchuan, Xiao, Yuan, Zhang, Yinqian, Lin, Zhiqiang, Lai, Ten H.·2019·2019 IEEE European Symposium on Security and Privacy (EuroS&P)

Abstract

Speculative execution side-channel vulnerabilities in micro-architecture processors have raised concerns about the security of Intel SGX. To understand clearly the security impact of this vulnerability against SGX, this paper makes the following studies: First, to demonstrate the feasibility of the attacks, we present SgxPectre Attacks (the SGX-variants of Spectre attacks) that exploit speculative execution side-channel vulnerabilities to subvert the confidentiality of SGX enclaves. We show that when the branch prediction of the enclave code can be influenced by programs outside the enclave, the control flow of the enclave program can be temporarily altered to execute instructions that lead to observable cache-state changes. An adversary observing such changes can learn secrets inside the enclave memory or its internal registers, thus completely defeating the confidentiality guarantee offered by SGX. Second, to determine whether real-world enclave programs are impacted by the attacks, we develop techniques to automate the search of vulnerable code patterns in enclave binaries using symbolic execution. Our study suggests that nearly any enclave program could be vulnerable to SgxPectre Attacks since vulnerable code patterns are available in most SGX runtimes (e.g., Intel SGX SDK, Rust-SGX, and Graphene-SGX). Third, we apply SgxPectre Attacks to steal seal keys and attestation keys from Intel signed quoting enclaves. The seal key can be used to decrypt sealed storage outside the enclaves and forge valid sealed data; the attestation key can be used to forge attestation signatures. For these reasons, SgxPectre Attacks practically defeat SGX's security protection. Finally, we evaluate Intel's existing countermeasures against SgxPectre Attacks and discusses the security implications.

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1109/eurosp.2019.00020

Cites

74 of 74 references verified0 citation errors · 0 not checkable

Statistics

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • An attestation server could be launched by the processor manufacturer, as with Intel's SGX attestation service, which is distinct from the cloud service provider.

    “An attestation server could be launched by the processor manufacturer, as with Intel's SGX attestation service [27], which is distinct from the cloud service provider.”

    From Confidential Computing Across Edge‐To‐Cloud for Machine Learning: A Survey Study (2025) · cites this paper as [27]

    The ‘Defense via Centralized Attestation Services’ section says Intel’s attestation service arbitrates attestation requests from the ISV, supporting the Intel SGX example. Our copy does not establish the claimed distinction between that service and a cloud service provider. (LLM, conf=0.82)

    Experimental — accuracy not yet measured
  • Intel SGX employs a memory encryption engine to provide assured secrecy, integrity, and freshness of CPU-DRAM traffic within enclave memory ranges.

    “Intel Software Guard Extensions (SGX) [27] employs a memory encryption engine to provide assured secrecy, integrity, and freshness of the CPU-DRAM traffic within the enclave memory ranges.”

    From Confidential Computing Across Edge‐To‐Cloud for Machine Learning: A Survey Study (2025) · cites this paper as [27]

    Section B, “Intel SGX” (page not available), identifies memory encryption as an SGX primitive and says enclave memory is protected for confidentiality and integrity. Our copy does not establish the more specific claim that a memory encryption engine assures freshness of CPU–DRAM traffic. (LLM, conf=0.84)

    Experimental — accuracy not yet measured
  • Intel SGX provides a remote attestation policy that evaluates the enclave identity, the integrity of the code inside it, and guarantees the authenticity of the Intel processor.

    “Intel SGX provides remote attestation policy that evaluates the enclave identity, integrity of the code inside of it, and guarantees the authenticity of the Intel processor.”

    From Confidential Computing Across Edge‐To‐Cloud for Machine Learning: A Survey Study (2025) · cites this paper as [27]

    The Remote Attestation section (page not provided) says attestation is used to prove that a claimed enclave runs on an SGX-enabled processor, supporting the enclave and processor-verification aspects. It does not explicitly say that attestation evaluates the integrity of the code inside the enclave. The Extracting attestation key section also demonstrates that a stolen key can produce a valid quote without running the enclave on SGX, so processor authenticity is not guaranteed without qualification. (LLM, conf=0.86)

    Experimental — accuracy not yet measured
  • Intel SGX proposes dynamic memory isolation to limit potential damage from side-channel attacks by isolating memory regions during execution phases.

    “Intel SGX proposes dynamic memory isolation to limit the potential damage from side-channel attacks by isolating memory regions during the execution phases.”

    From Confidential Computing Across Edge‐To‐Cloud for Machine Learning: A Survey Study (2025) · cites this paper as [27]

    The Intel SGX section describes enclave memory isolation during execution, and the Introduction says it protects code and data from other software. Neither section describes the isolation as dynamic or says it is proposed to limit damage from side-channel attacks; the paper’s “Leaking Secrets via Side Channels” section instead describes how such attacks can leak enclave information. Page numbers are unavailable in our copy. (LLM, conf=0.86)

    Experimental — accuracy not yet measured
  • Dynamic memory isolation reduces exposure to timing-based attacks and improves the security of confidential processing.

    “This approach reduces exposure to timing-based attacks and improves the security of the confidential processing [27].”

    From Confidential Computing Across Edge‐To‐Cloud for Machine Learning: A Survey Study (2025) · cites this paper as [27]

    The paper’s “Leaking Secrets via Side Channels” section (page unavailable) says enclave memory is not shared with the outside world, preventing ordinary FLUSH+RELOAD attacks. But it also explains how SGXPECTRE can use that timing-based channel despite the separation. The copy does not establish that dynamic memory isolation, as an approach, improves the security of confidential processing. (LLM, conf=0.78)

    Experimental — accuracy not yet measured

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Cites

Flagged first, then by citations

Research works printed but not linked: 6

  1. Y. Ding, R. Duan, L. Li, Y. Cheng, Y. Zhang, T. Chen, T. Wei, and H. Wang, "Poster: Rust SGX SDK: Towards memory safety in Intel SGX enclave," in ACM Conference on Computer and Communications Security, 2017.
  2. D. Kuvaiskii, O. Oleksenko, S. Arnautov, B. Trach, P. Bhatotia, P. Felber, and C. Fetzer, "Sgxbounds: Memory safety for shielded execution," in 12th European Conference on Computer Systems. ACM, 2017.
  3. G. Maisuradze and C. Rossow, "ret2spec: Speculative execution using return stack buffers," ArXiv e-prints, Jul. 2018.
  4. R. Martin, J. Demme, and S. Sethumadhavan, "Timewarp: rethinking timekeeping and performance monitoring mechanisms to mitigate side- channel attacks," in 39th Annual International Symposium on Computer Architecture, 2012.
  5. J. Van Bulck, F. Piessens, and R. Strackx, "SGX-Step: A practical attack framework for precise enclave execution control," in Proceedings of the 2Nd Workshop on System Software for Trusted Execution, ser. SysTEX'17. New York, NY, USA: ACM, 2017, pp. 4:1-4:6.
  6. F. Zhang, E. Cecchetti, K. Croman, A. Juels, , and E. Shi, "Town crier: An authenticated data feed for smart contracts," in 23rd ACM SIGSAC Conference on Computer and Communications Security. ACM, 2016.

Cited by

Sorted by citations

Authors
Chen, G., Chen, S., Xiao, Y., Zhang, Y., Lin, Z., & Lai, T. H.
Affiliations
The Ohio State University (US)
Venue
2019 IEEE European Symposium on Security and Privacy (EuroS&P)
Publisher
IEEE
Published
2019-06
Pages
142-157
OpenAlex
W2807403537
Cited by
319
References
74
Citations by year
2026: 16 · 2025: 36 · 2024: 43 · 2023: 43 · 2022: 41 · 2021: 55 · 2020: 51 · 2019: 25 · 2018: 8 · 2017: 1
FWCI
16.45
Type
conference paper
Language
en
Open access
Locations
  • IEEE European Symposium on Security and Privacy (publishedVersion)
  • arXiv (Cornell University) (submittedVersion)
Funders
National Science Foundation (1718084, 1750809, 1834215, 1834213)
Topics
  • Physical Sciences › Computer Science › Artificial Intelligence › Security and Verification in Computing
  • Physical Sciences › Computer Science › Artificial Intelligence › Cryptographic Implementations and Security
  • Physical Sciences › Computer Science › Artificial Intelligence › Cryptography and Data Security
Keywords
Intel SGX, Spectre attacks, branch prediction, cache side-channel, symbolic execution

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review