CVE-2019-6524 json
Moxa IKS and EDS do not implement sufficient measures to prevent multiple failed authentication attempts, which may allow an attacker to di…
published 7y ago modified 4mo ago also EUVD-2019-16083
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
Moxa IKS and EDS do not implement sufficient measures to prevent multiple failed authentication attempts, which may allow an attacker to discover passwords via brute force attack.
Is CVE-2019-6524 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-19-057-01 updated cvss 9.8
Moxa IKS, EDS (Update A)
-
Moxa EDS-405A series <= 3.8 Moxa EDS-408A series <= 3.8 Moxa EDS-510A series <= 3.8 Moxa IKS-G6824A series <= 5.6affected: mitigation “Install firmware patch. Patches may be requested from Moxa Customer Service (login required):” 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.73% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- ICS-CERT Moxa IKS, EDS
Classification
- Weakness
-
- CWE-307 Improper Restriction of Excessive Authentication Attempts
References
-
ics-cert.us-cert.gov
/advisories/ICSA-19-057-01
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/107178
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2019-6524
- NVD CVE-2019-6524
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.