CVE-2017-16719 json
An Injection issue was discovered in Moxa NPort 5110 Version 2.2, NPort 5110 Version 2.4, NPort 5110 Version 2.6, NPort 5110 Version 2.7, N…
published 2017-11-16 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-7903
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
An Injection issue was discovered in Moxa NPort 5110 Version 2.2, NPort 5110 Version 2.4, NPort 5110 Version 2.6, NPort 5110 Version 2.7, NPort 5130 Version 3.7 and prior, and NPort 5150 Version 3.7 and prior. An attacker may be able to inject packets that could potentially disrupt the availability of the device.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-17-320-01 updated cvss 7.5
Moxa NPort 5110, 5130, and 5150
-
Moxa NPort 5110 2.4, 2.7, 2.6, 2.2 Moxa NPort 5130 <= 3.7 Moxa NPort 5150 <= 3.7affected: vendor fix, mitigation “NPort 5110 https://www.moxa.com/support/download.aspx?type=support&id=882” moxa.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
2.22% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- n/a Moxa NPort 5110, 5130, and 5150
Classification
- Weakness
-
- CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component
References
-
securityfocus.com
/bid/101885
vdb-entry, third-party-advisory
-
ics-cert.us-cert.gov
/advisories/ICSA-17-320-01
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2017-16719
- NVD CVE-2017-16719
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.