CVE-2018-3608

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability in Trend Micro Maximum Security's (Consumer) 2018 (versions 12.0.1191 and below) User-Mode Hooking (UMH) driver could allow an attacker to create a specially crafted packet that could alter a vulnerable system in such a way that malicious code could be injected into other processes.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
65(Track*)
EG Risk 65/100SSVC: Track*

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
Severity98% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
3%
EPSS %ILE
88%
KEV
Not listed

Published

July 6, 2018

Last Modified

November 21, 2024

References (4)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× 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.

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

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

Publicly available exploits

(1 reference)

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

  • GitHub PoCgguaiker/Trend_Micro_POC
    First seen Feb 5, 2018

    CVE-2018-3608 Trend_Micro_CVE

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-3608?
CVE-2018-3608 is a critical vulnerability published on July 6, 2018. A vulnerability in Trend Micro Maximum Security's (Consumer) 2018 (versions 12.0.1191 and below) User-Mode Hooking (UMH) driver could allow an attacker to create a specially crafted packet that could alter a vulnerable system in such a way that malicious code could be injected into other processes.
When was CVE-2018-3608 disclosed?
CVE-2018-3608 was first published in the National Vulnerability Database on July 6, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-3608 actively exploited?
CVE-2018-3608 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 11.6% of all scored CVEs.
What is the CVSS score of CVE-2018-3608?
CVE-2018-3608 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-3608?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-3608, 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-2018-3608

Explore →

Is Your Infrastructure Affected by CVE-2018-3608?

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

Book a Demo →Browse All CVEs