What is CVE-2017-5754?A medium-severity flaw in Atom C, explained.

Medium severity209 affected products
The short answer

CVE-2017-5754 is a medium-severity flaw (CVSS 5.6) in Atom C from Intel, published on 4 January 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 84%. If you run an affected version, plan in the vendor’s fix.

Published 4 January 2018. Record last updated 19 November 2021. We keep this page's data up to date.

What it does

What is CVE-2017-5754? 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.

The official description

Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.

What kind of flaw is it?

  • CWE-200Exposure of Sensitive Information to an Unauthorized Actor
CVSS 3.0 scoreMedium · 5.6

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.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploitation

Is CVE-2017-5754 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 84%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days84%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
  3. Exploit likelihood fell
  4. Exploit likelihood jumped
How Precursor Intelligence ranks it
52out of 100Medium

CVE-2017-5754 scores 52. Action: Plan remediation.

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-2017-5754 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2017-5754? 209 products.

The published record lists 209 products from 2 vendors. If you run one of these, check your version, then go to the fix below.

  • Hardware

    Atom C

    by Intel

    Affected versions
    c2308c2316c2338c2350c2358c2508c2516c2518c2530c2538c2550c2558c2718c2730
  • Hardware

    Core I5

    by Intel

    Affected versions
    430m430um450m460m470um480m
  • Hardware

    Core I7

    by Intel

    Affected versions
    7y75610e620le620lm620m620ue
  • Hardware

    Core I3

    by Intel

    Affected versions
    330e330m330um350m370m380m
  • Hardware

    Xeon E5

    by Intel

    Affected versions
    2650l_v42658a_v326582658_v22658_v32658_v4
  • Hardware

    Xeon

    by Intel

    Affected versions
    e5502e5503e5504e5506e5507e5520
  • Hardware

    Xeon E7

    by Intel

    Affected versions
    28032820283028502850_v22860
  • Hardware

    Xeon Gold

    by Intel

    Affected versions
    511551185119t51205120t5122
  • Hardware

    Atom Z

    by Intel

    Affected versions
    z2420z2460z2480z2520z2560z2580
Remediation

How do I fix CVE-2017-5754? Four steps.

  1. 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.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
  3. 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.
  4. 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.
Precursor Intelligence

Does CVE-2017-5754 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2017-5754 is a medium-severity flaw in Atom C from Intel, published on 4 January 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-2017-5754 is 52 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.

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 84%. That can change at any time, which is why we keep watching.

For Atom C from Intel: c2308, c2316, c2338, c2350, c2358, c2508 and 26 more. The record lists 209 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.