CVE-2018-5407

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekElevated
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 3.4%CVSS: 4.7Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attacks via a side-channel timing attack on 'port contention'.

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
37
EG Risk 37/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
3.4%
EPSS %ILE
88th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

November 15, 2018

Last Modified

October 8, 2026

Advisory Details (8)

Auto-updated Oct 8, 2026
Patch available. Sources: redhat.
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2019:3935
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2019:3933
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 6.

https://access.redhat.com/errata/RHSA-2019:3932
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2019:3931
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, and Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2019:3929
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2019:2125
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2019:0483
generic

CVE-2018-5407 - PSIRT.COM

http://www.securityfocus.com/bid/105897

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibssl1.1 (1.1.1-1ubuntu2.1) @ cosmic2026-10-08ubuntu
redhatjbcs-httpd24-openssl-1:1.1.1-25.jbcs.el62019-11-20redhat
redhatopenssl2019-11-20redhat
redhatjbcs-httpd24-openssl-1:1.1.1-25.jbcs.el72019-11-20redhat
redhatjws5-tomcat-vault-0:1.1.8-1.Final_redhat_1.1.el8jws2019-11-20redhat
redhatovmf-0:20180508-6.gitee3198e672e2.el72019-08-06redhat
redhatrhvm-appliance-0:4.3-20190409.0.el72019-05-08redhat
redhatredhat-virtualization-host-0:4.3-20190409.0.el7_62019-05-08redhat
redhatopenssl-1:1.0.2k-16.el7_6.12019-03-13redhat

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

(13 across 12 ecosystems)
Debian:9(2)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.0f-3 ... 1.1.0h-4 (12 versions)
  • every version up to 1.1.0j-1~deb9u1: fixed in 1.1.0j-1~deb9u1
—
openssl1.01.0.2l-2 ... 1.0.2o-1+riscv64 (11 versions)
  • every version up to 1.0.2q-1~deb9u1: fixed in 1.0.2q-1~deb9u1
—
Alpine:v3.3(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.0.2q-r0: fixed in 1.0.2q-r0
—
Alpine:v3.4(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.0.2q-r0: fixed in 1.0.2q-r0
—
Alpine:v3.5(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.0.2q-r0: fixed in 1.0.2q-r0
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.0.2q-r0: fixed in 1.0.2q-r0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.0.2q-r0: fixed in 1.0.2q-r0
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.0.2q-r0: fixed in 1.0.2q-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1~~pre9-1: fixed in 1.1.1~~pre9-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1~~pre9-1: fixed in 1.1.1~~pre9-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1~~pre9-1: fixed in 1.1.1~~pre9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1~~pre9-1: fixed in 1.1.1~~pre9-1
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.0.1k-3 ... 1.0.1t-1+deb8u9 (16 versions)
  • every version up to 1.0.1t-1+deb8u10: fixed in 1.0.1t-1+deb8u10
—

Weakness Classification(2)

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

All Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 11× in last 7d / 29× 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.

Showing the most recent 100 of 170 total refreshes for this CVE.

  1. 2026-10-09 20:03 UTCEPSS rescore
  2. 2026-10-08 22:31 UTCVendor advisory
  3. 2026-10-08 22:31 UTCGHSA enrichment
  4. 2026-10-08 21:35 UTCEG score recompute
  5. 2026-10-08 21:35 UTCVendor advisory
  6. 2026-10-08 21:35 UTCGHSA enrichment
  7. 2026-10-08 16:37 UTCEPSS rescore
  8. 2026-10-07 23:42 UTCEPSS rescore
  9. 2026-10-06 15:12 UTCEPSS rescore
  10. 2026-10-05 17:39 UTCEPSS rescore
  11. 2026-10-03 14:21 UTCEPSS rescore
  12. 2026-10-01 19:44 UTCEPSS rescore
  13. 2026-09-30 14:59 UTCEPSS rescore
  14. 2026-09-30 10:02 UTCEG score recompute
  15. 2026-09-29 15:12 UTCEPSS rescore
  16. 2026-09-28 16:42 UTCOSV refresh
  17. 2026-09-28 13:46 UTCEPSS rescore
  18. 2026-09-27 13:40 UTCEPSS rescore
  19. 2026-09-26 15:53 UTCEPSS rescore
  20. 2026-09-24 13:59 UTCEPSS rescore
  21. 2026-09-23 13:42 UTCEPSS rescore
  22. 2026-09-21 20:27 UTCEPSS rescore
  23. 2026-09-19 15:36 UTCEPSS rescore
  24. 2026-09-18 19:22 UTCEPSS rescore
  25. 2026-09-17 19:22 UTCEPSS rescore
Show 75 more
  1. 2026-09-15 03:05 UTCEPSS rescore
  2. 2026-09-15 03:05 UTCEPSS rescore
  3. 2026-09-11 14:48 UTCEPSS rescore
  4. 2026-09-11 09:32 UTCEPSS rescore
  5. 2026-09-08 21:34 UTCOSV refresh
  6. 2026-09-06 13:44 UTCEPSS rescore
  7. 2026-09-04 13:56 UTCEPSS rescore
  8. 2026-09-04 05:02 UTCEPSS rescore
  9. 2026-09-02 14:07 UTCEPSS rescore
  10. 2026-09-01 03:32 UTCEPSS rescore
  11. 2026-08-30 19:13 UTCEPSS rescore
  12. 2026-08-30 01:18 UTCEPSS rescore
  13. 2026-08-28 21:36 UTCEPSS rescore
  14. 2026-08-27 14:21 UTCEPSS rescore
  15. 2026-08-26 14:42 UTCEPSS rescore
  16. 2026-08-25 13:45 UTCEPSS rescore
  17. 2026-08-24 14:11 UTCEPSS rescore
  18. 2026-08-22 06:37 UTCOSV refresh
  19. 2026-08-21 23:45 UTCEPSS rescore
  20. 2026-08-20 22:51 UTCEPSS rescore
  21. 2026-08-19 17:00 UTCEPSS rescore
  22. 2026-08-18 13:44 UTCEPSS rescore
  23. 2026-08-17 13:43 UTCEPSS rescore
  24. 2026-08-16 14:52 UTCEPSS rescore
  25. 2026-08-16 02:10 UTCEPSS rescore
  26. 2026-08-15 01:26 UTCEPSS rescore
  27. 2026-08-13 21:56 UTCEPSS rescore
  28. 2026-08-12 13:47 UTCEPSS rescore
  29. 2026-08-08 16:32 UTCEPSS rescore
  30. 2026-08-07 16:23 UTCEPSS rescore
  31. 2026-08-06 13:42 UTCEPSS rescore
  32. 2026-08-06 09:40 UTCOSV refresh
  33. 2026-08-04 15:05 UTCEPSS rescore
  34. 2026-08-04 10:33 UTCEPSS rescore
  35. 2026-08-03 10:31 UTCEPSS rescore
  36. 2026-08-02 02:23 UTCEPSS rescore
  37. 2026-08-01 04:12 UTCEPSS rescore
  38. 2026-07-30 16:24 UTCEPSS rescore
  39. 2026-07-30 01:27 UTCEPSS rescore
  40. 2026-07-28 15:32 UTCEPSS rescore
  41. 2026-07-27 14:05 UTCEPSS rescore
  42. 2026-07-26 14:51 UTCEPSS rescore
  43. 2026-07-25 14:14 UTCEPSS rescore
  44. 2026-07-25 14:14 UTCEPSS rescore
  45. 2026-07-24 14:14 UTCEPSS rescore
  46. 2026-07-24 14:14 UTCEPSS rescore
  47. 2026-07-23 14:15 UTCEPSS rescore
  48. 2026-07-23 14:15 UTCEPSS rescore
  49. 2026-07-23 01:36 UTCEG score recompute
  50. 2026-07-22 22:17 UTCEG score recompute
  51. 2026-07-22 14:05 UTCEPSS rescore
  52. 2026-07-21 15:22 UTCEPSS rescore
  53. 2026-07-21 02:47 UTCOSV refresh
  54. 2026-07-20 17:04 UTCEPSS rescore
  55. 2026-07-20 17:04 UTCEPSS rescore
  56. 2026-07-19 14:28 UTCEPSS rescore
  57. 2026-07-19 14:28 UTCEPSS rescore
  58. 2026-07-19 02:26 UTCEPSS rescore
  59. 2026-07-19 02:26 UTCEPSS rescore
  60. 2026-07-16 16:59 UTCEPSS rescore
  61. 2026-07-16 16:59 UTCEPSS rescore
  62. 2026-07-15 16:55 UTCEPSS rescore
  63. 2026-07-15 01:56 UTCEPSS rescore
  64. 2026-07-13 22:27 UTCEPSS rescore
  65. 2026-07-13 06:10 UTCEPSS rescore
  66. 2026-07-12 05:43 UTCEPSS rescore
  67. 2026-07-09 19:06 UTCEPSS rescore
  68. 2026-07-08 15:11 UTCEPSS rescore
  69. 2026-07-08 15:11 UTCEPSS rescore
  70. 2026-07-07 13:42 UTCEPSS rescore
  71. 2026-07-07 13:42 UTCEPSS rescore
  72. 2026-07-06 16:25 UTCEPSS rescore
  73. 2026-07-06 16:24 UTCEPSS rescore
  74. 2026-07-06 02:20 UTCEPSS rescore
  75. 2026-07-05 02:27 UTCEPSS rescore

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-45785
    First seen Nov 2, 2018

    Intel (Skylake / Kaby Lake) - 'PortSmash' CPU SMT Side-Channel

    Open source ↗

Frequently asked(5)

What is CVE-2018-5407?
CVE-2018-5407 is a medium vulnerability published on November 15, 2018. Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attacks via a side-channel timing attack on 'port contention'.
When was CVE-2018-5407 disclosed?
CVE-2018-5407 was first published on November 15, 2018, with the most recent update on October 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-5407 actively exploited?
CVE-2018-5407 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.4% probability of exploitation in the next 30 days (88th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-5407?
CVE-2018-5407 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2018-5407?
A fix for CVE-2018-5407 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2018-5407 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-2018-5407

Explore →

Is Your Infrastructure Affected by CVE-2018-5407?

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