Auto-Maskin RP210E/DCU210E/Marine Observer Pro weak password
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Auto-Maskin RP210E, DCU210E and Marine Observer Pro. It has been classified as problematic. This affects an unknown function. This manipulation causes weak password. This vulnerability is tracked as CVE-2019-6558. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Auto-Maskin RP210E, DCU210E and Marine Observer Pro (unknown version). It has been declared as critical. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a weak password vulnerability. The CWE definition for the vulnerability is CWE-521. The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In Auto-Maskin RP210E Versions 3.7 and prior, DCU210E Versions 3.7 and prior and Marine Observer Pro (Android App), the software contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.
The weakness was disclosed 03/23/2020. This vulnerability is known as CVE-2019-6558 since 01/22/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entry VDB-152018 is pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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
Class: Weak passwordCWE: CWE-521
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
01/22/2019 🔍03/23/2020 🔍
03/24/2020 🔍
03/24/2020 🔍
Sources
Status: Not definedCVE: CVE-2019-6558 (🔍)
GCVE (CVE): GCVE-0-2019-6558
GCVE (VulDB): GCVE-100-152017
See also: 🔍
Entry
Created: 03/24/2020 08:09Updated: 03/24/2020 08:14
Changes: 03/24/2020 08:09 (35), 03/24/2020 08:14 (17)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.