CVE-2018-3640: Systems with microprocessors utilizing speculative execution and that perform speculative reads of system registers may allow unauthorized…
Noroxi assessment
Priority: Monitor (action score 24/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: 7.1% (FIRST EPSS); higher than 94.3% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: intel-microcode (Debian:12) 3.20180703.1; intel-microcode (Debian:8) 3.20180703.2~deb8u1; intel-microcode (Debian:9) 3.20180807a.1~deb9u1, 3.20180703.2~deb9u1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to intel-microcode (Debian:12) 3.20180703.1; intel-microcode (Debian:8) 3.20180703.2~deb8u1; intel-microcode (Debian:9) 3.20180807a.1~deb9u1, 3.20180703.2~deb9u1 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 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.
- Published
- May 22, 2018
- Updated
- Jun 16, 2026
- EPSS
- 7.1% · 94th percentile
- CWE
- CWE-203
Report tools
Action score
24
Low priority for now.
- CVSS
- 22 / 40 · 5.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 7.1%
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 | atom c | cpe:2.3:h:intel:atom_c |
| intel | atom e | cpe:2.3:h:intel:atom_e |
| intel | atom z | cpe:2.3:h:intel:atom_z |
| intel | celeron j | cpe:2.3:h:intel:celeron_j |
| intel | celeron n | cpe:2.3:h:intel:celeron_n |
| 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 | core m | cpe:2.3:h:intel:core_m |
| intel | pentium | cpe:2.3:h:intel:pentium |
| intel | pentium j | cpe:2.3:h:intel:pentium_j |
| intel | pentium silver | cpe:2.3:h:intel:pentium_silver |
and 187 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 atom cc2308
- intel atom cc3308
- intel atom cc3338
- intel atom cc3508
- intel atom cc3538
- intel atom cc3558
- intel atom cc3708
- intel atom cc3750
- intel atom cc3758
- intel atom cc3808
- intel atom cc3830
- intel atom cc3850
- intel atom cc3858
- intel atom cc3950
- intel atom cc3955
- intel atom cc3958
- intel atom ee3805
- intel atom ee3815
- intel atom ee3825
- intel atom ee3826
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 |
| Debian:8 | intel-microcode | before 3.20180703.2~deb8u1 | 3.20180703.2~deb8u1 |
| Debian:9 | intel-microcode | before 3.20180807a.1~deb9u1 | 3.20180807a.1~deb9u1 |
| Debian:9 | intel-microcode | before 3.20180703.2~deb9u1 | 3.20180703.2~deb9u1 |
| openSUSE:Tumbleweed | spectre-meltdown-checker | before 26.36.0602723-1.1 | 26.36.0602723-1.1 |
| openSUSE:Tumbleweed | ucode-intel | before 20210608-1.2 | 20210608-1.2 |
| SUSE:Linux Enterprise Module for Basesystem 15 | ucode-intel | before 20180703-3.3.1 | 20180703-3.3.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | ucode-intel | before 20180807-3.6.1 | 20180807-3.6.1 |
| SUSE:Linux Enterprise Point of Sale 11 SP3 | microcode_ctl | before 1.17-102.83.27.1 | 1.17-102.83.27.1 |
| SUSE:Linux Enterprise Point of Sale 11 SP3 | microcode_ctl | before 1.17-102.83.24.1 | 1.17-102.83.24.1 |
| SUSE:OpenStack Cloud 7 | ucode-intel | before 20180807-13.29.1 | 20180807-13.29.1 |
| SUSE:OpenStack Cloud 7 | ucode-intel | before 20180703-13.25.1 | 20180703-13.25.1 |
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-5753Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an…50Plan
- CVE-2017-5715Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of…44Plan
- CVE-2017-5754Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of…42Plan
Published before and after this one in the same product
- ← EarlierCVE-2018-9056Mar 27, 2018 · Systems with microprocessors utilizing speculative execution may allow unauthorized disclosure of information to an attacker with local…22Monitor
- ← EarlierCVE-2018-3639May 22, 2018 · Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addresses of all prior…40Plan
- Later →CVE-2018-3693Jul 10, 2018 · Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of information to an…25Monitor
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) |
| opensuse:ucode-intel | 20210608-1.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:microcode_ctl | 1.17-102.83.24.1 · SUSE:Linux Enterprise Point of Sale 11 SP3 | Package registry (OSV) |
| suse:ucode-intel | 20180703-3.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 | 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
- ArmIntigriti · paid · up to $20,000
- Intel® Vulnerability Disclosure Program Intigriti · disclosure only (VDP)
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ı)
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-203 · Observable DiscrepancyCVSS vector
CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
nvd-primary
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 (19 more)Show less
- www.fujitsu.com/global/support/products/software/security/products-f/cve-2018-3639e.html
- www.securityfocus.com/bid/104228
- www.securitytracker.com/id/1040949
- www.securitytracker.com/id/1042004
- cert-portal.siemens.com/productcert/pdf/ssa-268644.pdf
- cert-portal.siemens.com/productcert/pdf/ssa-608355.pdf
- developer.arm.com/support/arm-security-updates/speculative-processor-vulnerability
- lists.debian.org/debian-lts-announce/2018/07/msg00038.html
- lists.debian.org/debian-lts-announce/2018/09/msg00017.html
- portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV180013
- psirt.global.sonicwall.com/vuln-detail/SNWLID-2018-0005
- security.netapp.com/advisory/ntap-20180521-0001/
- support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03850en_us
- tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180521-cpusidechannel
- usn.ubuntu.com/3756-1/
- www.debian.org/security/2018/dsa-4273
- www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00115.html
- www.kb.cert.org/vuls/id/180049
- www.mitel.com/en-ca/support/security-advisories/mitel-product-security-advisory-18-0006
Vendor advisories and official records. Exploit/PoC links are deliberately left out.