No exploitation reported

CVE-2016-8379

No exploitation reported by the sources we read.

Published2017-02-13

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC

2017-02-1321:59CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-8379?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-8379?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Moxa iologik e1200 series firmwareversion to verify

Branch	Affected	Fixed in	Source
2.4	≤ 2.4	no fix published	NVD
2.3	≤ 2.3	no fix published	NVD
2.5	≤ 2.5	no fix published	NVD

Moxa iologik e2200 series firmwareversion to verify

Branch	Affected	Fixed in	Source
3.11	≤ 3.11	no fix published	NVD
3.12	≤ 3.12	no fix published	NVD
3.13	≤ 3.13	no fix published	NVD

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.18.1read 2026-10-23
NVDCVSS 2.04.3read 2026-10-23
FIRST EPSSEPSS score1.4 %2026-10-22

Technical details

CVSS v3 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Published: 2017-02-13
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2016-8379?

Is CVE-2016-8379 actively exploited?

Active exploitation of CVE-2016-8379 has not been confirmed. Its EPSS score was 1.4% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2016-8379?

CVE-2016-8379 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database