Motorola MOSCAD Toolbox up to 2022-05-02 Configuration File wmdlcdrv.ini cleartext storage in file
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Motorola MOSCAD Toolbox up to 2022-05-02. This affects an unknown function of the file wmdlcdrv.ini of the component Configuration File Handler. Such manipulation leads to cleartext storage in file. This vulnerability is documented as CVE-2022-30275. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability was found in Motorola MOSCAD Toolbox up to 2022-05-02. It has been rated as critical. Affected by this issue is an unknown functionality of the file wmdlcdrv.ini of the component Configuration File Handler. The manipulation with an unknown input leads to a cleartext storage in file vulnerability. Using CWE to declare the problem leads to CWE-313. The product stores sensitive information in cleartext in a file, or on disk. Impacted is confidentiality. CVE summarizes:
The Motorola MOSCAD Toolbox software through 2022-05-02 relies on a cleartext password. It utilizes an MDLC driver to communicate with MOSCAD/ACE RTUs for engineering purposes. Access to these communications is protected by a password stored in cleartext in the wmdlcdrv.ini driver configuration file. In addition, this password is used for access control to MOSCAD/STS projects protected with the Legacy Password feature. In this case, an insecure CRC of the password is present in the project file: this CRC is validated against the password in the driver configuration file.
The weakness was released 07/27/2022 as icsa-22-179-05. The advisory is shared for download at cisa.gov. This vulnerability is handled as CVE-2022-30275 since 05/04/2022. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1555.
By approaching the search of inurl:wmdlcdrv.ini 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.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Cleartext storage in fileCWE: CWE-313 / CWE-312 / CWE-310
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
05/04/2022 🔍07/27/2022 🔍
07/27/2022 🔍
07/27/2022 🔍
Sources
Advisory: icsa-22-179-05Status: Not defined
CVE: CVE-2022-30275 (🔍)
GCVE (CVE): GCVE-0-2022-30275
GCVE (VulDB): GCVE-100-205136
Entry
Created: 07/27/2022 14:30Changes: 07/27/2022 14:30 (40)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.