# CVE-2018-3615: Information disclosure in Multiple

> Local attackers can exploit speculative execution to read sensitive data from Intel SGX enclaves via side-channel analysis.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/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:** 14 Aug 2018
- **Updated:** 29 May 2026
- **Also known as:** DEBIAN-CVE-2018-3615, GHSA-9w6j-7396-jgw4

## What is CVE-2018-3615?

CVE-2018-3615 is a high-severity vulnerability in Intel Corporation Multiple, published on 14 Aug 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 Intel software guard extensions (Intel SGX) may allow unauthorized disclosure of information residing in the L1 data cache from an enclave to an attacker with local user access via a side-channel analysis.

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 30 products.


Products: Intel Core I3, Intel Core I5, Intel Core I7, Intel Xeon E3, Intel Xeon E3 1220 V5, Intel Xeon E3 1220 V6, Intel Xeon E3 1225 V5, Intel Xeon E3 1225 V6, Intel Xeon E3 1230 V5, Intel Xeon E3 1230 V6, Intel Xeon E3 1235l V5, Intel Xeon E3 1240 V5, Intel Xeon E3 1240 V6, Intel Xeon E3 1240l V5, Intel Xeon E3 1245 V5, Intel Xeon E3 1245 V6, Intel Xeon E3 1260l V5, Intel Xeon E3 1268l V5, Intel Xeon E3 1270 V5, Intel Xeon E3 1270 V6 and 10 more.

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

Apply the vendor's patch.

## Is CVE-2018-3615 being exploited?

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

## Other vulnerabilities in Intel Corporation Multiple

- [CVE-2018-12169](https://insights.sbomify.com/CVE-2018-12169/): Auth bypass in n/a (high 7.6)
- [CVE-2017-5704](https://insights.sbomify.com/CVE-2017-5704/): Information disclosure in Intel Core Processor (medium 6.7)
- [CVE-2018-3620](https://insights.sbomify.com/CVE-2018-3620/): Information disclosure in Multiple (medium 5.6)
- [CVE-2018-3646](https://insights.sbomify.com/CVE-2018-3646/): Information disclosure in Multiple (medium 5.6)
- [CVE-2018-3619](https://insights.sbomify.com/CVE-2018-3619/): Information disclosure in Intel Optane memory (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-3615 is a high-severity vulnerability in Intel Corporation Multiple, published on 14 Aug 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-3615 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-3615/ (Markdown: https://insights.sbomify.com/CVE-2018-3615/index.md)
```

## Sources

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

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