# CVE-2020-8766: Denial of service in Intel(R) SGX DCAP software

> An unauthenticated attacker can cause a denial of service in Intel SGX DCAP software via adjacent access due to improper condition checks.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3xfq-3889-4q8m

## What is CVE-2020-8766?

CVE-2020-8766 is a medium-severity denial of service vulnerability in Intel(R) SGX DCAP software, published on 12 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper conditions check in the Intel(R) SGX DCAP software before version 1.6 may allow an unauthenticated user to potentially enable denial of service via adjacent access.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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

It affects 1 product.


Products: Intel Software Guard Extensions Data Center Attestation Primitives.

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

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

## Is CVE-2020-8766 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8766 is a medium-severity denial of service vulnerability in Intel(R) SGX DCAP software, published on 12 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-8766 in the wild and no public exploit code.

Affected product: Intel(R) SGX DCAP software. 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-8766/ (Markdown: https://insights.sbomify.com/CVE-2020-8766/index.md)
```

## Sources

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

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