Skip to content
Noroxi
CVE-2018-3615· NVD / CVE Program· CNA intel

Systems with microprocessors utilizing speculative execution and Intel software guard extensions (Intel SGX) may allow unauthorized disclosu

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.

HighCVSS 7.3 · v3.1—No exploit Fix available
Published
Aug 14, 2018
Updated
Jun 16, 2026
EPSS
6.3% · 93th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
29 / 40 · 7.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 6.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Affected systems

VendorProduct
intelcore i3
intelcore i5
intelcore i7
intelxeon e3
intelxeon e3 1220 v5
intelxeon e3 1225 v5
intelxeon e3 1230 v5
intelxeon e3 1235l v5
intelxeon e3 1240 v5
intelxeon e3 1240l v5
intelxeon e3 1245 v5
intelxeon e3 1260l v5

and 18 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • intel core i36006u
  • intel core i36098p
  • intel core i36100
  • intel core i36100e
  • intel core i36100h
  • intel core i36100t
  • intel core i36100te
  • intel core i36100u
  • intel core i36102e
  • intel core i36157u
  • intel core i36167u
  • intel core i36300
  • intel core i36300t
  • intel core i36320
  • intel core i38100
  • intel core i38350k
  • intel core i56200u
  • intel core i56260u
  • intel core i56267u
  • intel core i56287u

Versions reported by the vendor

Affected version ranges reported by the assigning authority (intel). Independent of NVD's CPE analysis and usually ahead of it.

  • Intel Corporation Multiple

    • Multipleaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12intel-microcodebefore 3.20180703.13.20180703.1
openSUSE:Tumbleweedspectre-meltdown-checkerbefore 26.36.0602723-1.126.36.0602723-1.1

Other highest-scoring records for the same primary product.

  • CVE-2018-12169Platform sample code firmware in 4th Generation Intel Core Processor, 5th Generation Intel Core Processor, 6th Generation Intel Core Process
    30Monitor
  • CVE-2017-5704Platform sample code firmware included with 4th Gen Intel Core Processor, 5th Gen Intel Core Processor, 6th Gen Intel Core Processor, and 7t
    26Monitor
  • CVE-2018-3646Systems with microprocessors utilizing speculative execution and address translations may allow unauthorized disclosure of information resid
    25Monitor
  • CVE-2018-3620Systems with microprocessors utilizing speculative execution and address translations may allow unauthorized disclosure of information resid
    24Monitor
  • CVE-2018-3665System software utilizing Lazy FP state restore technique on systems using Intel Core-based microprocessors may potentially allow a local pr
    22Monitor
  • CVE-2020-24491Debug message containing addresses of memory transactions in some Intel(R) 10th Generation Core Processors supporting SGX may allow a privil
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:intel-microcode3.20180703.1 · Debian:12Package registry (OSV)
opensuse:spectre-meltdown-checker26.36.0602723-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
low · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
Low
Availability impact
None

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records