# CVE-2018-3640: Information disclosure in Multiple

> Local attackers can exploit speculative execution to disclose system parameters via side-channel analysis on Intel microprocessors.

- **Severity:** Medium 5.6 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/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:** 22 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-3640, GHSA-wm4v-x65g-m25r, UBUNTU-CVE-2018-3640

## What is CVE-2018-3640?

CVE-2018-3640 is a medium-severity vulnerability in Intel Corporation Multiple, published on 22 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized disclosure of system parameters to an attacker with local user access via a side-channel analysis, aka Rogue System Register Read (RSRE), Variant 3a.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2018-3640?

It affects 199 products.


Products: Arm Cortex-A, Intel Atom C, Intel Atom E, Intel Atom Z, Intel Celeron J, Intel Celeron N, Intel Core I3, Intel Core I5, Intel Core I7, Intel Core M, Intel Pentium, Intel Pentium J, Intel Pentium Silver, Intel Xeon E-1105c, Intel Xeon E3, Intel Xeon E3 1105c V2, Intel Xeon E3 1125c V2, Intel Xeon E3 12201, Intel Xeon E3 12201 V2, Intel Xeon E3 1220 V2 and 179 more.

## How do I fix CVE-2018-3640?

Apply the vendor's patch.

## Is CVE-2018-3640 being exploited?

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

## Other vulnerabilities in Intel Corporation Multiple

- [CVE-2018-3693](https://insights.sbomify.com/CVE-2018-3693/): Information disclosure in Most Modern Operating Systems (medium 5.6)
- [CVE-2018-9056](https://insights.sbomify.com/CVE-2018-9056/): Information disclosure in n/a (medium 5.6)
- [CVE-2017-5715](https://insights.sbomify.com/CVE-2017-5715/): Information disclosure in Microprocessors with Speculative Execution (medium 5.6)
- [CVE-2017-5754](https://insights.sbomify.com/CVE-2017-5754/): Information disclosure in Most Modern Operating Systems (medium 5.6)
- [CVE-2018-3639](https://insights.sbomify.com/CVE-2018-3639/): Information disclosure in Multiple (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3640 and fix it if it is affected.

What it is: CVE-2018-3640 is a medium-severity vulnerability in Intel Corporation Multiple, published on 22 May 2018. 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-2018-3640 in the wild and no public exploit code.

Affected product: Intel Corporation Multiple. 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-2018-3640/ (Markdown: https://insights.sbomify.com/CVE-2018-3640/index.md)
```

## Sources

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

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