What is CVE-2018-3665?A medium-severity flaw in Core I3, explained.
CVE-2018-3665 is a medium-severity flaw (CVSS 5.6) in Core I3 from Intel, published on 21 June 2018. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.6%. If you run an affected version, plan in the vendor’s fix.
Published 21 June 2018. Record last updated 9 June 2021. We keep this page's data up to date.
What is CVE-2018-3665? In plain terms.
An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data.
System software utilizing Lazy FP state restore technique on systems using Intel Core-based microprocessors may potentially allow a local process to infer data from another process through a speculative execution side channel.
What kind of flaw is it?
- CWE-200Exposure of Sensitive Information to an Unauthorized Actor
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAlready on the device
- How hard it is to pull offHard: conditions must line up
- Login needed firstAn ordinary user account
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data
Severity vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
Is CVE-2018-3665 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.6%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2018-3665 scores 18. Action: Track.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2018-3665 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2018-3665? 14 products.
The published record lists 14 products from 6 vendors. If you run one of these, check your version, then go to the fix below.
- Hardware
Core I3
by Intel
Affected versions330e330m330um350m370m380m380um390m53054055056021002100t - Hardware
Core I5
by Intel
Affected versions430m430um450m460m470um480m - Hardware
Core I7
by Intel
Affected versions7y75610e620le620lm620m620ue - Hardware
Core M
by Intel
Affected versions5y10a5y105y10c5y315y515y70 - Application
Xenserver
by Citrix
Affected versions7.07.17.37.47.5 - Hardware
Core M3
by Intel
Affected versions6y307y307y32 - Operating system
FreeBSD
by FreeBSD
Affected versions11.011.111.2 - Operating system
Ubuntu Linux
by Canonical
Affected versions12.0414.0416.04 - Hardware
Core M5
by Intel
Affected versions6y546y57
How do I fix CVE-2018-3665? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2018-3665 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
System software utilizing Lazy FP state restore technique on systems using Intel Core-based microprocessors may potentially allow a local process to infer da...
- Matched to
- Core I3 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2018-3665 is a medium-severity flaw in Core I3 from Intel, published on 21 June 2018. An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data.
It scores 5.6 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2018-3665 is 18 out of 100, which is Info. Its action is "Track". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.6%. That can change at any time, which is why we keep watching.
For Core I3 from Intel: 330e, 330m, 330um, 350m, 370m, 380m and 106 more. The record lists 14 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.