# CVE-2020-5499: Race condition in n/a

> A race condition in the Baidu Rust SGX SDK can cause duplicate enclave IDs, potentially leading to unpredictable behavior or security issues in trusted execution environments.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mm2c-2xqg-7v99

## What is CVE-2020-5499?

CVE-2020-5499 is a critical vulnerability in n/a, published on 4 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Baidu Rust SGX SDK through 1.0.8 has an enclave ID race. There are non-deterministic results in which, sometimes, two global IDs are the same.

## Which versions are affected by CVE-2020-5499?

It affects 1 product.


Products: Apache Rust Sgx Sdk.

## How do I fix CVE-2020-5499?

No fix has been published for CVE-2020-5499 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-5499 being exploited?

There is no known exploitation of CVE-2020-5499 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-5499 and fix it if it is affected.

What it is: CVE-2020-5499 is a critical vulnerability in n/a, published on 4 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-5499 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-5499/ (Markdown: https://insights.sbomify.com/CVE-2020-5499/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-5499
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-5499
- OSV: https://osv.dev/vulnerability/CVE-2020-5499

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-5499/
Summaries are generated and may contain mistakes; the official description above is the record.