# CVE-2020-8698: Information disclosure in Intel(R) Processors

> An authenticated local attacker can exploit improper resource isolation in Intel processors to disclose sensitive information.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2020-8698, DEBIAN-CVE-2020-8698, GHSA-9636-925v-53qr, UBUNTU-CVE-2020-8698

## What is CVE-2020-8698?

CVE-2020-8698 is a medium-severity vulnerability in Debian Debian Linux, 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 isolation of shared resources in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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

It affects 17 products.


Products: Debian Debian Linux, Fedoraproject Fedora, Intel Microcode, Netapp Clustered Data Ontap, Netapp Hci Compute Node Bios, Netapp Hci Storage Node Bios, Netapp Solidfire Bios, Siemens Simatic Field Pg M5 Firmware, Siemens Simatic Field Pg M6 Firmware, Siemens Simatic Ipc427e Firmware, Siemens Simatic Ipc477e Firmware, Siemens Simatic Ipc477e Pro Firmware, Siemens Simatic Ipc627e Firmware, Siemens Simatic Ipc647e Firmware, Siemens Simatic Ipc677e Firmware, Siemens Simatic Ipc847e Firmware, Siemens Simatic Itp1000 Firmware.

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

Apply the vendor's patch.

## Is CVE-2020-8698 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8698 is a medium-severity vulnerability in Debian Debian Linux, 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-8698 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-8698/ (Markdown: https://insights.sbomify.com/CVE-2020-8698/index.md)
```

## Sources

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

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