CVE-2017-5715

MEDIUMNVD 5.69.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 89% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 5.6 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
5.6
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 74%
CISA-KEV: Not listedEPSS: 74%CVSS: 5.6Exploit: NoneExposed: 0

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
9.0(high)
EPSS
99.4%
KEV
Not listed

Published

January 4, 2018

Last Modified

May 6, 2025

References (188)

Vendor Advisories for CVE-2017-5715(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-image-generic-lts-trusty (3.13.0.140.131) @ precise2026-05-28ubuntu
ubuntulinux-image-extra-4.13.0-36-generic (4.13.0-36.40~16.04.1) @ xenial2026-05-28ubuntu
ubuntulibwebkit2gtk-4.0-37 (2.18.5-0ubuntu0.17.04.1) @ zesty2026-05-28ubuntu
ubuntulinux-image-extra-3.13.0-143-generic (3.13.0-143.192) @ trusty2026-05-28ubuntu
ubuntulinux-image-3.2.0-133-generic (3.2.0-133.179) @ precise2026-05-28ubuntu
ubuntulinux-image-extra-4.4.0-9023-euclid (4.4.0-9023.24) @ xenial2026-05-28ubuntu
ubuntulinux-image-extra-4.13.0-31-generic (4.13.0-31.34~16.04.1) @ xenial2026-05-28ubuntu
redhatkernel-alt-0:4.14.0-49.8.1.el7a2018-06-26redhat
redhatkernel-0:2.6.32-696.28.1.el62018-05-08redhat
redhatkernel-0:2.6.32-573.55.2.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-693.25.2.el72018-04-17redhat
redhatkernel-0:3.10.0-514.48.1.el72018-04-17redhat
redhatlibvirt-0:3.9.0-14.el72018-04-10redhat
redhatkernel-0:3.10.0-862.el72018-04-10redhat
redhatlinux-firmware-0:20180220-62.git6d51311.el72018-04-10redhat
redhatmicrocode_ctl-2:2.1-29.el72018-04-10redhat
redhatqemu-kvm-ma-10:2.10.0-21.el72018-04-10redhat
redhatkernel-rt-1:3.10.0-693.11.1.rt56.606.el6rt2018-01-04redhat
redhatdracut-0:033-502.el7_4.12018-01-04redhat
redhatqemu-kvm-10:1.5.3-126.el7_3.132018-01-04redhat
redhatqemu-kvm-10:1.5.3-141.el7_4.62018-01-04redhat
redhatkernel-0:2.6.32-358.84.2.el62018-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
redhatkernel-0:2.6.32-504.64.4.el62018-01-04redhat
redhatkernel-0:2.6.32-220.76.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.

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 3× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-11 08:24 UTCEPSS rescore
  2. 2026-07-06 02:20 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-04 15:26 UTCOSV refresh
  5. 2026-07-04 06:28 UTCEPSS rescore
  6. 2026-07-01 15:02 UTCEPSS rescore
  7. 2026-06-30 23:19 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-28 14:04 UTCEPSS rescore
  10. 2026-06-28 04:53 UTCEPSS rescore
  11. 2026-06-25 13:47 UTCEPSS rescore
  12. 2026-06-24 14:02 UTCEPSS rescore
  13. 2026-06-24 14:02 UTCEPSS rescore
  14. 2026-06-23 21:30 UTCEPSS rescore
  15. 2026-06-17 17:50 UTCEPSS rescore
  16. 2026-06-16 17:50 UTCEPSS rescore
  17. 2026-06-16 17:50 UTCEPSS rescore
  18. 2026-06-16 03:13 UTCOSV refresh
  19. 2026-06-15 17:45 UTCEPSS rescore
  20. 2026-06-13 22:57 UTCEPSS rescore
  21. 2026-06-12 23:09 UTCEPSS rescore
  22. 2026-06-10 22:15 UTCEPSS rescore
  23. 2026-06-10 13:19 UTCEPSS rescore
  24. 2026-06-08 14:14 UTCEPSS rescore
  25. 2026-06-08 14:14 UTCEPSS rescore
Show 16 more
  1. 2026-06-07 15:22 UTCEPSS rescore
  2. 2026-06-07 15:22 UTCEPSS rescore
  3. 2026-06-05 22:44 UTCEPSS rescore
  4. 2026-06-05 06:08 UTCEPSS rescore
  5. 2026-06-05 06:08 UTCEPSS rescore
  6. 2026-06-04 13:10 UTCEPSS rescore
  7. 2026-05-31 00:14 UTCEPSS rescore
  8. 2026-05-31 00:14 UTCEPSS rescore
  9. 2026-05-29 13:41 UTCEPSS rescore
  10. 2026-05-28 13:42 UTCEPSS rescore
  11. 2026-05-28 13:42 UTCEPSS rescore
  12. 2026-05-28 12:54 UTCEG score recompute
  13. 2026-05-28 12:54 UTCVendor advisory
  14. 2026-05-26 07:17 UTCEPSS rescore
  15. 2026-05-26 07:17 UTCEPSS rescore
  16. 2026-05-23 02:35 UTCOSV refresh

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCmathse/meltdown-spectre-bios-list
    First seen 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
    First seen Jan 9, 2018

    Spectre exploit

    Open source ↗
  • Exploit-DBEDB-43427
    First seen 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 medium vulnerability 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 disclosed?
CVE-2017-5715 was first published in the National Vulnerability Database on January 4, 2018, with the most recent update on May 6, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-5715 actively exploited?
CVE-2017-5715 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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 + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2017-5715?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-5715, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs