Skip to main content
No exploitation reported

CVE-2018-3615

No exploitation reported by the sources we read.

  • Published2018-08-14
  • WeaknessCWE-203

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2018-08-1419:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2018-3615?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-3615?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Intel core i3
BranchAffectedFixed in
6006.x= 6006uno fix published
6098.x= 6098pno fix published
6100.x= 6100no fix published
6100.x= 6100eno fix published
6100.x= 6100hno fix published
6100.x= 6100tno fix published
6100.x= 6100teno fix published
6100.x= 6100uno fix published
6102.x= 6102eno fix published
6157.x= 6157uno fix published
6167.x= 6167uno fix published
6300.x= 6300no fix published
Intel core i5
BranchAffectedFixed in
650.x= 650no fix published
655.x= 655kno fix published
660.x= 660no fix published
661.x= 661no fix published
670.x= 670no fix published
680.x= 680no fix published
6200.x= 6200uno fix published
6260.x= 6260uno fix published
6267.x= 6267uno fix published
6287.x= 6287uno fix published
6300.x= 6300hqno fix published
6300.x= 6300uno fix published
Intel core i7
BranchAffectedFixed in
610.x= 610eno fix published
620.x= 620leno fix published
620.x= 620lmno fix published
620.x= 620mno fix published
620.x= 620ueno fix published
620.x= 620umno fix published
640.x= 640lmno fix published
640.x= 640mno fix published
640.x= 640umno fix published
660.x= 660lmno fix published
660.x= 660ueno fix published
660.x= 660umno fix published

27 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2026-05-29
  • OpenCVESSVC decisionnone—
  • CISA-ADPCVSS 3.17.32026-05-29
  • NVDCVSS 3.06.4read 2026-10-23
  • NVDCVSS 2.05.4read 2026-10-23
  • CISA-ADPweakness (CWE)CWE-2032026-05-29
  • NVDweakness (CWE)CWE-203read 2026-10-23
  • FIRST EPSSEPSS score6.3 %2026-10-22

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
Published
2018-08-14
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2018-3615?

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.

Is CVE-2018-3615 actively exploited?

Active exploitation of CVE-2018-3615 has not been confirmed. Its EPSS score was 6.3% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2018-3615?

CVE-2018-3615 has a CVSS v3 base score of 7.3 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database