MOXA NPort 5110 Out-of-bounds Write
Priority MEDIUM 40CWE-787Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-787 and the CVSS impact.
Summary
MOXA NPort 5110: Firmware Versions 2.10 is vulnerable to an out-of-bounds write that can cause the device to become unresponsive.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00851 58th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Moxa | MOXA | Firmware Versions 2.10 | — | No fix listed | CNA |
- MOXA VendorMoxa Affected Firmware Versions 2.10 Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2022-2043
- 2026-10-03 Alias added: GHSA-w4r2-5c62-qrmc
References
More Moxa Nport 5110 Firmware vulnerabilities
- TI-2017-12284 Information disclosure in Moxa NPort 5110, 5130, and 5150 CVSS 3.1HIGH 8.6
- TI-2022-01894 MOXA NPort 5110 Out-of-bounds Write CVSS 3.1HIGH 8.2
- TI-2023-04539 NPort 5000 Series Firmware Improper Validation of Integrity Check Vulnerability CVSS 3.1HIGH 8.8
- TI-2017-12288 Injection in Moxa NPort 5110, 5130, and 5150 CVSS 3.0HIGH 7.5
- TI-2017-10210 Uncontrolled resource consumption in Moxa NPort 5110, 5130, and 5150 CVSS 3.0HIGH 7.5
Sources
- CVE-2022-2043 · CVE Program
- CVE-2022-2043 · NVD
- FIRST EPSS
- GHSA-w4r2-5c62-qrmc · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences