Mitsubishi Electric ME-RTU/INEA ME-RTU Configuration File settings.xml Credentials default permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Mitsubishi Electric ME-RTU and INEA ME-RTU. The impacted element is an unknown function of the file /usr/smartrtu/init/settings.xml of the component Configuration File. Executing a manipulation can lead to default permission (Credentials). This vulnerability is registered as CVE-2019-14925. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability was found in Mitsubishi Electric ME-RTU and INEA ME-RTU (affected version unknown). It has been declared as problematic. This vulnerability affects an unknown functionality of the file /usr/smartrtu/init/settings.xml of the component Configuration File. The manipulation with an unknown input leads to a default permission vulnerability (Credentials). The CWE definition for the vulnerability is CWE-276. During installation, installed file permissions are set to allow anyone to modify those files. As an impact it is known to affect confidentiality. CVE summarizes:
An issue was discovered on Mitsubishi Electric ME-RTU devices through 2.02 and INEA ME-RTU devices through 3.0. A world-readable /usr/smartrtu/init/settings.xml configuration file on the file system allows an attacker to read sensitive configuration settings such as usernames, passwords, and other sensitive RTU data due to insecure permission assignment.
The weakness was published 10/28/2019. This vulnerability was named CVE-2019-14925 since 08/10/2019. The exploitation appears to be easy. The attack can be initiated remotely. The successful exploitation needs a single authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1222 by the MITRE ATT&CK project.
By approaching the search of inurl:usr/smartrtu/init/settings.xml it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-144254, VDB-144253, VDB-144252 and VDB-144251. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: CredentialsClass: Default permission / Credentials
CWE: CWE-276 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/10/2019 🔍10/28/2019 🔍
10/28/2019 🔍
09/10/2024 🔍
Sources
Advisory: mogozobo.comStatus: Not defined
CVE: CVE-2019-14925 (🔍)
GCVE (CVE): GCVE-0-2019-14925
GCVE (VulDB): GCVE-100-144250
See also: 🔍
Entry
Created: 10/28/2019 20:08Updated: 09/10/2024 20:18
Changes: 10/28/2019 20:08 (37), 10/28/2019 20:13 (17), 01/29/2024 10:02 (3), 09/10/2024 20:18 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.