CVE-2020-5499Public exploit

Application crash via concurrent enclave initialization

Published Jan 4, 2020 · Updated Aug 4, 2024

Race condition in Baidu Rust SGX SDK 1.0.8 and earlier allows attackers to crash enclave applications during concurrent enclave creation. The t_global_init_ecall path stores an enclave identifier in global state without preserving distinct values across concurrent initialization calls. Triggering the demonstrated failure requires two local threads to initialize enclaves concurrently on a Linux host with Intel SGX hardware; the duplicate identifier causes the application to crash.

CVSS severity9.8
Critical
EPSS probability3.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Race condition in Baidu Rust SGX SDK 1.0.8 and earlier allows attackers to crash enclave applications during concurrent enclave creation. The t_global_init_ecall path stores an enclave identifier in global state without preserving distinct values across concurrent initialization calls. Triggering the demonstrated failure requires two local threads to initialize enclaves concurrently on a Linux host with Intel SGX hardware; the duplicate identifier causes the application to crash.

The record

CVE
CVE-2020-5499
Published
Jan 4, 2020
Updated
Aug 4, 2024
Vendor
Unknown vendor
Product
Unknown product
Classifications
T1499.004
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Jan 4, 2020CVE publishedPublication date reported by the CVE source.
  2. 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?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

7.5NIST NVDAV:N/AC:L/Au:N/C:P/I:P/A:P
9.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

T1499.004Application or System Exploitation

Public exploit references

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