CVE-2017-5715

HIGHNVD 5.68.3
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 8.3 because EPSS predicted 73% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 5.6 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekWeaponized

Also known asEUVD-2017-14792 (ENISA EUVD)Source: ENISA EUVD

8.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 73%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 73%CVSS: 5.6Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.6
EG Score
8.3HIGHhigh confidence
EG Risk
54
EG Risk 54/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity56% × 45%
Impact severity (EG Severity): CVSS 5.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation73% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
73%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.3): severity, escalated by confirmed exploitation. This CVE's 8.3 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 5.6 MEDIUM): a likelihood of exploitation, not impact.

EG Severity
5.6 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
73% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 4, 2018

Last Modified

May 6, 2025

References (94)

15 of 94 shown · show the other 79

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-image-extra-4.13.0-36-generic (4.13.0-36.40~16.04.1) @ xenial2026-10-29ubuntu
ubuntulinux-image-generic-lts-trusty (3.13.0.144.135) @ precise2026-10-29ubuntu
ubuntulinux-image-raspi2 (4.13.0.1015.13) @ artful2026-10-29ubuntu
ubuntulinux-image-generic (4.13.0.31.33) @ artful2026-10-29ubuntu
ubuntulinux-image-extra-4.4.0-116-generic (4.4.0-116.140) @ xenial2026-10-29ubuntu
ubuntulinux-image-extra-3.13.0-141-generic (3.13.0-141.190) @ trusty2026-10-29ubuntu
ubuntulinux-image-generic-lts-trusty (3.13.0.140.131) @ precise2026-10-29ubuntu
redhatkernel-alt-0:4.14.0-49.8.1.el7a2018-06-26redhat
redhatkernel-0:2.6.32-573.55.2.el62018-05-08redhat
redhatkernel-0:2.6.32-696.28.1.el62018-05-08redhat
redhatkernel-0:2.6.18-348.39.1.el52018-04-25redhat
redhatkernel-0:3.10.0-327.66.1.el72018-04-24redhat
redhatkernel-0:2.6.18-430.el52018-04-23redhat
redhatkernel-0:3.10.0-514.48.1.el72018-04-17redhat
redhatkernel-0:3.10.0-693.25.2.el72018-04-17redhat
redhatlinux-firmware-0:20180220-62.git6d51311.el72018-04-10redhat
redhatqemu-kvm-ma-10:2.10.0-21.el72018-04-10redhat
redhatlibvirt-0:3.9.0-14.el72018-04-10redhat
redhatkernel-0:3.10.0-862.el72018-04-10redhat
redhatmicrocode_ctl-2:2.1-29.el72018-04-10redhat
redhatkernel-0:2.6.32-220.76.2.el62018-01-04redhat
redhatdracut-0:033-502.el7_4.12018-01-04redhat
redhatkernel-rt-1:3.10.0-693.11.1.rt56.606.el6rt2018-01-04redhat
redhatqemu-kvm-10:1.5.3-126.el7_3.132018-01-04redhat
redhatqemu-kvm-rhev-10:2.6.0-28.el7_3.152018-01-04redhat
redhatkernel-rt-0:3.10.0-693.11.1.rt56.639.el72018-01-04redhat
redhatkernel-0:2.6.32-431.85.2.el62018-01-04redhat
redhatqemu-kvm-10:1.5.3-141.el7_4.62018-01-04redhat
redhatkernel-0:2.6.32-504.64.4.el62018-01-04redhat
redhatkernel-0:2.6.32-358.84.2.el62018-01-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(37 across 9 ecosystems)
Debian:12(7)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20171205.2 (25 versions)
  • every version up to 3.20180515.1: fixed in 3.20180515.1
—
arm-trusted-firmware2.10.0+dfsg-1 ... 2.9.0+dfsg-3 (10 versions)
  • every version on: no fix on record
—
intel-microcode0.20080131-1 ... 3.20180425.1~deb9u1 (95 versions)
  • every version up to 3.20180425.1: fixed in 3.20180425.1
—
linux—
  • every version up to 4.15.11-1: fixed in 4.15.11-1
—
nvidia-graphics-drivers1.0.6629+1-2 ... 384.98-3~bpo9+1 (350 versions)
  • every version up to 384.111-1: fixed in 384.111-1
—
qemu—
  • every version up to 1:2.12~rc3+dfsg-1: fixed in 1:2.12~rc3+dfsg-1
—
xen—
  • every version up to 4.11.1~pre+1.733450b39b-1: fixed in 4.11.1~pre+1.733450b39b-1
—
Debian:13(7)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20171205.2 (25 versions)
  • every version up to 3.20180515.1: fixed in 3.20180515.1
—
arm-trusted-firmware2.12.1+dfsg-1, 2.12.16+dfsg-1
  • every version on: no fix on record
—
intel-microcode0.20080131-1 ... 3.20180425.1~deb9u1 (95 versions)
  • every version up to 3.20180425.1: fixed in 3.20180425.1
—
linux—
  • every version up to 4.15.11-1: fixed in 4.15.11-1
—
nvidia-graphics-drivers1.0.6629+1-2 ... 384.98-3~bpo9+1 (350 versions)
  • every version up to 384.111-1: fixed in 384.111-1
—
qemu—
  • every version up to 1:2.12~rc3+dfsg-1: fixed in 1:2.12~rc3+dfsg-1
—
xen—
  • every version up to 4.11.1~pre+1.733450b39b-1: fixed in 4.11.1~pre+1.733450b39b-1
—
Debian:14(7)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20171205.2 (25 versions)
  • every version up to 3.20180515.1: fixed in 3.20180515.1
—
arm-trusted-firmware2.12.1+dfsg-1
  • every version up to 2.12.16+dfsg-1: fixed in 2.12.16+dfsg-1
—
intel-microcode0.20080131-1 ... 3.20180425.1~deb9u1 (95 versions)
  • every version up to 3.20180425.1: fixed in 3.20180425.1
—
linux—
  • every version up to 4.15.11-1: fixed in 4.15.11-1
—
nvidia-graphics-drivers1.0.6629+1-2 ... 384.98-3~bpo9+1 (350 versions)
  • every version up to 384.111-1: fixed in 384.111-1
—
qemu—
  • every version up to 1:2.12~rc3+dfsg-1: fixed in 1:2.12~rc3+dfsg-1
—
xen—
  • every version up to 4.11.1~pre+1.733450b39b-1: fixed in 4.11.1~pre+1.733450b39b-1
—
Debian:11(6)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20171205.2 (25 versions)
  • every version up to 3.20180515.1: fixed in 3.20180515.1
—
intel-microcode0.20080131-1 ... 3.20180425.1~deb9u1 (95 versions)
  • every version up to 3.20180425.1: fixed in 3.20180425.1
—
linux—
  • every version up to 4.15.11-1: fixed in 4.15.11-1
—
nvidia-graphics-drivers1.0.6629+1-2 ... 384.98-3~bpo9+1 (350 versions)
  • every version up to 384.111-1: fixed in 384.111-1
—
qemu—
  • every version up to 1:2.12~rc3+dfsg-1: fixed in 1:2.12~rc3+dfsg-1
—
xen—
  • every version up to 4.11.1~pre+1.733450b39b-1: fixed in 4.11.1~pre+1.733450b39b-1
—
Debian:9(4)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20181128.1~deb8u1 (30 versions)
  • every version up to 3.20181128.1~deb9u1: fixed in 3.20181128.1~deb9u1
—
linux4.9.30-2 ... 4.9.88-1~bpo8+1 (25 versions)
  • every version up to 4.9.88-1: fixed in 4.9.88-1
—
qemu1:2.8+dfsg-6, 1:2.8+dfsg-6+deb9u1, 1:2.8+dfsg-6+deb9u2, 1:2.8+dfsg-6+deb9u3
  • every version up to 1:2.8+dfsg-6+deb9u4: fixed in 1:2.8+dfsg-6+deb9u4
—
xen4.8.1-1+deb9u1 ... 4.8.3+comet2+shim4.10.0+comet3-1+deb9u5 (7 versions)
  • every version up to 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u6: fixed in 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u6
—
Debian:8(3)
PackageVulnerable rangeFix by version rangeDependents
amd64-microcode0.20120117-1 ... 3.20181128.1~bpo9+1 (29 versions)
  • every version up to 3.20181128.1~deb8u1: fixed in 3.20181128.1~deb8u1
—
linux3.16.36-1 ... 3.16.7-ckt9-3~deb8u1~bpo70+1 (56 versions)
  • every version up to 3.16.57-1: fixed in 3.16.57-1
  • every version up to 3.16.56-1: fixed in 3.16.56-1
—
qemu1:2.1+dfsg-11 ... 1:2.1+dfsg-12~bpo70+1 (12 versions)
  • every version up to 1:2.1+dfsg-12+deb8u7: fixed in 1:2.1+dfsg-12+deb8u7
—
Alpine:v3.5(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.7.3-r4: fixed in 4.7.3-r4
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.8.2-r4: fixed in 4.8.2-r4
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
linux3.2.41-2 ... 3.2.96-3 (71 versions)
  • every version up to 3.2.101-1: fixed in 3.2.101-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(22)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 26× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 89 of 98 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 11 repeat rows among the latest 100 are merged into the row they repeat. The 9 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-31 16:27 UTCEPSS rescoreEPSS 73% · 99th percentile
  2. 2026-10-29 12:54 UTCEG score recompute
  3. 2026-10-29 12:54 UTCVendor advisory
  4. 2026-10-28 16:27 UTCEPSS rescoreEPSS 73% · 99th percentile
  5. 2026-10-27 16:26 UTCEPSS rescoreEPSS 73% · 99th percentile
  6. 2026-10-26 16:26 UTCEPSS rescoreEPSS 73% · 99th percentile
  7. 2026-10-25 19:32 UTCEG score recompute
  8. 2026-10-25 16:27 UTCEPSS rescoreEPSS 73% · 99th percentile
  9. 2026-10-23 16:26 UTCEPSS rescoreEPSS 74% · 99th percentile
  10. 2026-10-22 02:57 UTCEG score recompute
  11. 2026-10-22 02:57 UTCVendor advisory
  12. 2026-10-21 16:27 UTCEPSS rescoreEPSS 74% · 99th percentile
  13. 2026-10-20 16:27 UTCEPSS rescoreEPSS 74% · 99th percentile
  14. 2026-10-19 16:26 UTCEPSS rescoreEPSS 74% · 99th percentile
  15. 2026-10-18 10:29 UTCEG score recompute
  16. 2026-10-17 16:27 UTCEPSS rescoreEPSS 74% · 99th percentile
  17. 2026-10-16 16:29 UTCEPSS rescoreEPSS 74% · 99th percentile
  18. 2026-10-14 16:27 UTCEPSS rescoreEPSS 74% · 99th percentile
  19. 2026-10-13 16:27 UTCEPSS rescoreEPSS 74% · 99th percentile
  20. 2026-10-13 02:49 UTCVendor advisory
  21. 2026-10-12 20:27 UTCEG score recompute
  22. 2026-10-12 00:50 UTCEG score recompute
  23. 2026-10-11 13:41 UTCEPSS rescoreEPSS 74% · 99th percentile
  24. 2026-10-08 16:36 UTCEPSS rescoreEPSS 74% · 99th percentile
  25. 2026-10-07 23:41 UTCEPSS rescoreEPSS 74% · 99th percentile
Show 64 more
  1. 2026-10-05 17:38 UTCEPSS rescoreEPSS 74% · 99th percentile
  2. 2026-09-30 09:34 UTCEG score recompute
  3. 2026-09-29 11:53 UTCOSV refresh
  4. 2026-09-26 15:53 UTCEPSS rescoreEPSS 74% · 99th percentile
  5. 2026-09-24 13:59 UTCEPSS rescoreEPSS 74% · 99th percentile
  6. 2026-09-18 19:22 UTCEPSS rescoreEPSS 74% · 99th percentile
  7. 2026-09-17 19:22 UTCEPSS rescoreEPSS 74% · 99th percentile
  8. 2026-09-13 16:42 UTCEPSS rescoreEPSS 74% · 99th percentile
  9. 2026-09-12 14:55 UTCEPSS rescoreEPSS 74% · 99th percentile
  10. 2026-09-11 09:31 UTCEPSS rescoreEPSS 74% · 99th percentile
  11. 2026-09-09 22:23 UTCOSV refresh
  12. 2026-09-06 13:43 UTCEPSS rescoreEPSS 74% · 99th percentile
  13. 2026-09-05 15:23 UTCEPSS rescoreEPSS 74% · 99th percentile
  14. 2026-09-02 14:07 UTCEPSS rescoreEPSS 74% · 99th percentile
  15. 2026-08-30 19:13 UTCEPSS rescoreEPSS 74% · 99th percentile
  16. 2026-08-27 14:21 UTCEPSS rescoreEPSS 74% · 99th percentile
  17. 2026-08-26 14:41 UTCEPSS rescoreEPSS 74% · 99th percentile
  18. 2026-08-23 00:46 UTCOSV refresh
  19. 2026-08-21 23:44 UTCEPSS rescoreEPSS 74% · 99th percentile
  20. 2026-08-19 16:59 UTCEPSS rescoreEPSS 74% · 99th percentile
  21. 2026-08-16 02:10 UTCEPSS rescoreEPSS 74% · 99th percentile
  22. 2026-08-12 13:46 UTCEPSS rescoreEPSS 74% · 99th percentile
  23. 2026-08-07 16:22 UTCEPSS rescoreEPSS 74% · 99th percentile
  24. 2026-08-07 03:57 UTCOSV refresh
  25. 2026-08-05 19:12 UTCEPSS rescoreEPSS 74% · 99th percentile
  26. 2026-08-02 02:23 UTCEPSS rescoreEPSS 74% · 99th percentile
  27. 2026-07-30 16:24 UTCEPSS rescoreEPSS 74% · 99th percentile
  28. 2026-07-30 01:26 UTCEPSS rescoreEPSS 74% · 99th percentile
  29. 2026-07-26 14:51 UTCEPSS rescoreEPSS 74% · 99th percentile
  30. 2026-07-23 14:15 UTCEPSS rescoreEPSS 74% · 99th percentile
  31. 2026-07-23 01:30 UTCEG score recompute▲ 2.70
  32. 2026-07-22 22:09 UTCEG score recompute▼ 3.40
  33. 2026-07-22 14:04 UTCEPSS rescoreEPSS 74% · 99th percentile
  34. 2026-07-21 19:48 UTCOSV refresh
  35. 2026-07-20 17:04 UTCEPSS rescoreEPSS 74% · 99th percentile
  36. 2026-07-19 14:28 UTCEPSS rescoreEPSS 74% · 99th percentile
  37. 2026-07-18 10:00 UTCEPSS rescoreEPSS 74% · 99th percentile
  38. 2026-07-16 16:59 UTCEPSS rescoreEPSS 74% · 99th percentile
  39. 2026-07-15 16:54 UTCEPSS rescoreEPSS 74% · 99th percentile
  40. 2026-07-11 08:24 UTCEPSS rescoreEPSS 74% · 99th percentile
  41. 2026-07-06 02:20 UTCEPSS rescoreEPSS 74% · 99th percentile
  42. 2026-07-04 15:26 UTCOSV refresh
  43. 2026-07-04 06:28 UTCEPSS rescoreEPSS 74% · 99th percentile
  44. 2026-07-01 15:02 UTCEPSS rescoreEPSS 74% · 99th percentile
  45. 2026-06-30 23:19 UTCEPSS rescoreEPSS 74% · 99th percentile
  46. 2026-06-28 14:04 UTCEPSS rescoreEPSS 74% · 99th percentile
  47. 2026-06-28 04:53 UTCEPSS rescoreEPSS 74% · 99th percentile
  48. 2026-06-25 13:47 UTCEPSS rescoreEPSS 74% · 99th percentile
  49. 2026-06-24 14:02 UTCEPSS rescoreEPSS 74% · 99th percentile
  50. 2026-06-23 21:30 UTCEPSS rescoreEPSS 74% · 99th percentile
  51. 2026-06-17 17:50 UTCEPSS rescoreEPSS 74% · 99th percentile
  52. 2026-06-16 17:50 UTCEPSS rescoreEPSS 74% · 99th percentile
  53. 2026-06-16 03:13 UTCOSV refresh
  54. 2026-06-15 17:45 UTCEPSS rescoreEPSS 74% · 99th percentile
  55. 2026-06-13 22:57 UTCEPSS rescoreEPSS 88% · 99th percentile
  56. 2026-06-12 23:09 UTCEPSS rescoreEPSS 88% · 99th percentile
  57. 2026-06-10 22:15 UTCEPSS rescoreEPSS 88% · 99th percentile
  58. 2026-06-10 13:19 UTCEPSS rescoreEPSS 88% · 99th percentile
  59. 2026-06-08 14:14 UTCEPSS rescoreEPSS 88% · 99th percentile
  60. 2026-06-07 15:22 UTCEPSS rescoreEPSS 88% · 99th percentile
  61. 2026-06-05 22:44 UTCEPSS rescoreEPSS 88% · 99th percentile
  62. 2026-06-05 06:08 UTCEPSS rescoreEPSS 89% · 99th percentile
  63. 2026-06-04 13:10 UTCEPSS rescoreEPSS 89% · 99th percentile
  64. 2026-05-31 00:14 UTCEPSS rescoreEPSS 89% · 99th percentile

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (1 Exploit-DB entry, 2 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • GitHub PoCmathse/meltdown-spectre-bios-list
    Published Jan 14, 2018

    a list of BIOS/Firmware fixes adressing CVE-2017-5715, CVE-2017-5753, CVE-2017-5754

    Open source ↗
  • GitHub PoCopsxcq/exploit-cve-2017-5715
    Published Jan 9, 2018

    Spectre exploit

    Open source ↗
  • Exploit-DBEDB-43427
    Published Jan 3, 2018

    Multiple CPUs - 'Spectre' Information Disclosure

    Open source ↗

Past incidents using this CVE

(1)

This CVE was central to one or more publicly-documented breaches. Each card links to authoritative reporting at the time of the incident.

  • Spectre & Meltdown (CPU side-channel)Jan 2018

    Speculative-execution side-channel attacks against virtually every modern CPU (Intel, AMD, ARM). Required hardware-firmware updates and OS kernel changes across the industry.

    Source: ZDNet

Frequently asked(5)

What is CVE-2017-5715?
CVE-2017-5715 is a high-severity vulnerability; its CVE record was published on January 4, 2018. 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.
When was CVE-2017-5715 made public?
CVE-2017-5715 was made public on January 3, 2018: that is the date its CVE record's CNA, Intel Corporation, gives for when the vulnerability was made public. The CVE record itself was published on January 4, 2018. EchelonGraph's copy of the record carries a last-modified date of May 6, 2025; the record at its source may have been updated since.
Is CVE-2017-5715 actively exploited?
CVE-2017-5715 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 73% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-5715?
CVE-2017-5715 has a CVSS v3 base score of 5.6 (NVD). EchelonGraph synthesises NVD + FIRST EPSS into a combined EG score of 8.3 (HIGH).
How do I remediate CVE-2017-5715?
A fix for CVE-2017-5715 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-5715 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-5715

Explore →

Is Your Infrastructure Affected by CVE-2017-5715?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.