CVE-2016-5799 json
Moxa OnCell G3100V2 devices before 2.8 and G3111, G3151, G3211, and G3251 devices before 1.7 do not properly restrict authentication attemp…
published 2016-08-24 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-6734
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.0%
- EPSS 4.0% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
Moxa OnCell G3100V2 devices before 2.8 and G3111, G3151, G3211, and G3251 devices before 1.7 do not properly restrict authentication attempts, which makes it easier for remote attackers to obtain access via a brute-force attack.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-16-236-01A updated cvss 9.8
Moxa OnCell Vulnerabilities (Update A)
-
Moxa OnCell G3100V2 Series <2.8 Moxa OnCell G3111/G3151/G3211/G3251 Series <1.7affected: mitigation “Moxa has made firmware fixes available on their web site at the following locations: (http://www.moxa.com/support/sarch_result.aspx?type=soft&prod_id=316&type_id=4)”
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
4.00% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-285 Improper Authorization
References
-
ics-cert.us-cert.gov
/advisories/ICSA-16-236-01
mitigation, third-party-advisory, us-government-resource
-
securityfocus.com
/bid/92606
vdb-entry
Sources
- CVE List CVE-2016-5799
- NVD CVE-2016-5799
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.