CVE-2019-14930 json
An issue was discovered on Mitsubishi Electric Europe B.V.
published 2019-10-28 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-6028
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
An issue was discovered on Mitsubishi Electric Europe B.V. ME-RTU devices through 2.02 and INEA ME-RTU devices through 3.0. Undocumented hard-coded user passwords for root, ineaadmin, mitsadmin, and maint could allow an attacker to gain unauthorised access to the RTU. (Also, the accounts ineaadmin and mitsadmin are able to escalate privileges to root without supplying a password due to insecure entries in /etc/sudoers on the RTU.)
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-21-252-03 updated cvss 9.8
Mitsubishi Electric Europe B.V. smartRTU and INEA ME-RTU
-
Mitsubishi Electric smartRTU and INEA ME-RTU < 3.3affected: mitigation “Mitsubishi Electric Europe B.V. recommends users update to firmware Version 3.3 or later.” inea.si
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.34% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- mogozobo.com https://www.mogozobo.com/?p=3593 referenced PoC, tagged "exploit" by a source, unverified
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 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
mogozobo.com
/?p=3593
exploit, third-party-advisory
-
mogozobo.com
/
third-party-advisory
Sources
- CVE List CVE-2019-14930
- NVD CVE-2019-14930
Fencer Vulns 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.