CVE-2018-3615: Systems with microprocessors utilizing speculative execution and Intel software guard extensions (Intel SGX) may allow unauthorized…
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 6.3% (FIRST EPSS); higher than 93.7% of all records.
- 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.
- Fixed version: intel-microcode (Debian:12) 3.20180703.1; spectre-meltdown-checker (openSUSE:Tumbleweed) 26.36.0602723-1.1.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to intel-microcode (Debian:12) 3.20180703.1; spectre-meltdown-checker (openSUSE:Tumbleweed) 26.36.0602723-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 14, 2018
- Updated
- Jun 16, 2026
- EPSS
- 6.3% · 93th percentile
- CWE
- CWE-203
Report tools
Action score
31
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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| intel | core i3 | cpe:2.3:h:intel:core_i3 |
| intel | core i5 | cpe:2.3:h:intel:core_i5 |
| intel | core i7 | cpe:2.3:h:intel:core_i7 |
| intel | xeon e3 | cpe:2.3:h:intel:xeon_e3 |
| intel | xeon e3 1220 v5 | cpe:2.3:h:intel:xeon_e3_1220_v5 |
| intel | xeon e3 1225 v5 | cpe:2.3:h:intel:xeon_e3_1225_v5 |
| intel | xeon e3 1230 v5 | cpe:2.3:h:intel:xeon_e3_1230_v5 |
| intel | xeon e3 1235l v5 | cpe:2.3:h:intel:xeon_e3_1235l_v5 |
| intel | xeon e3 1240 v5 | cpe:2.3:h:intel:xeon_e3_1240_v5 |
| intel | xeon e3 1240l v5 | cpe:2.3:h:intel:xeon_e3_1240l_v5 |
| intel | xeon e3 1245 v5 | cpe:2.3:h:intel:xeon_e3_1245_v5 |
| intel | xeon e3 1260l v5 | cpe:2.3:h:intel:xeon_e3_1260l_v5 |
and 18 more
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
Affected versions · NVD (20)
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
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | intel-microcode | before 3.20180703.1 | 3.20180703.1 |
| openSUSE:Tumbleweed | spectre-meltdown-checker | before 26.36.0602723-1.1 | 26.36.0602723-1.1 |
Same product
intel: all recordsOther 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…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…26Monitor
- CVE-2018-3646Systems with microprocessors utilizing speculative execution and address translations may allow unauthorized disclosure of information…24Monitor
Published before and after this one in the same product
- ← EarlierCVE-2018-3665Jun 21, 2018 · System software utilizing Lazy FP state restore technique on systems using Intel Core-based microprocessors may potentially allow a local…22Monitor
- Later →CVE-2018-3620Aug 14, 2018 · Systems with microprocessors utilizing speculative execution and address translations may allow unauthorized disclosure of information…24Monitor
- Later →CVE-2020-24491Feb 17, 2021 · Debug message containing addresses of memory transactions in some Intel(R) 10th Generation Core Processors supporting SGX may allow a…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 / package | Fixed version | Source |
|---|---|---|
| debian:intel-microcode | 3.20180703.1 · Debian:12 | Package registry (OSV) |
| opensuse:spectre-meltdown-checker | 26.36.0602723-1.1 · openSUSE:Tumbleweed | Package 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.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-602 · Aug 12, 2020(Huawei Ürünleri için Güvenlik Güncellemesi Yayınladı)
- TR-18-104 · Aug 14, 2018 TR-18-104 (Intel Side-Channel L1TF Zafiyeti)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
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
Weakness class (CWE)
CWE-203 · Observable DiscrepancyCVSS 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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (16 more)Show less
- www.huawei.com/en/psirt/security-advisories/huawei-sa-20180815-01-cpu-en
- www.securityfocus.com/bid/105080
- www.securitytracker.com/id/1041451
- cert-portal.siemens.com/productcert/pdf/ssa-254686.pdf
- cert-portal.siemens.com/productcert/pdf/ssa-608355.pdf
- foreshadowattack.eu/
- lists.debian.org/debian-lts-announce/2018/09/msg00017.html
- psirt.global.sonicwall.com/vuln-detail/SNWLID-2018-0008
- security.netapp.com/advisory/ntap-20180815-0001/
- software.intel.com/security-software-guidance/software-guidance/l1-terminal-fault
- support.f5.com/csp/article/K35558453
- support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03874en_us
- tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180814-cpusidechannel
- www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00161.html
- www.kb.cert.org/vuls/id/982149
- www.synology.com/support/security/Synology_SA_18_45
Vendor advisories and official records. Exploit/PoC links are deliberately left out.