CVE-2016-8379

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.1Exploit: NoneExposed: 0

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

An issue was discovered in Moxa ioLogik E1210, firmware Version V2.4 and prior, ioLogik E1211, firmware Version V2.3 and prior, ioLogik E1212, firmware Version V2.4 and prior, ioLogik E1213, firmware Version V2.5 and prior, ioLogik E1214, firmware Version V2.4 and prior, ioLogik E1240, firmware Version V2.3 and prior, ioLogik E1241, firmware Version V2.4 and prior, ioLogik E1242, firmware Version V2.4 and prior, ioLogik E1260, firmware Version V2.4 and prior, ioLogik E1262, firmware Version V2.4 and prior, ioLogik E2210, firmware versions prior to V3.13, ioLogik E2212, firmware versions prior to V3.14, ioLogik E2214, firmware versions prior to V3.12, ioLogik E2240, firmware versions prior to V3.12, ioLogik E2242, firmware versions prior to V3.12, ioLogik E2260, firmware versions prior to V3.13, and ioLogik E2262, firmware versions prior to V3.12. Users are restricted to using short passwords.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity81% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
70.2%
KEV
Not listed

Published

February 13, 2017

Last Modified

May 13, 2026

References (4)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2016-8379?
CVE-2016-8379 is a high vulnerability published on February 13, 2017. An issue was discovered in Moxa ioLogik E1210, firmware Version V2.4 and prior, ioLogik E1211, firmware Version V2.3 and prior, ioLogik E1212, firmware Version V2.4 and prior, ioLogik E1213, firmware Version V2.5 and prior, ioLogik E1214, firmware Version V2.4 and prior, ioLogik E1240, firmware…
When was CVE-2016-8379 disclosed?
CVE-2016-8379 was first published in the National Vulnerability Database on February 13, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-8379 actively exploited?
CVE-2016-8379 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 70.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-8379?
CVE-2016-8379 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2016-8379?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-8379, 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-2016-8379

Explore →

Is Your Infrastructure Affected by CVE-2016-8379?

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

Start Free Scan →Browse All CVEs