Shenzhen Coship WM3300 5.0.0.55 Password Reset wl_security_2G.asp POST Request credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Shenzhen Coship WM3300 5.0.0.55. This issue affects some unknown processing of the file regx/wireless/wl_security_2G.asp of the component Password Reset. Such manipulation as part of POST Request leads to credentials management. This vulnerability is listed as CVE-2019-7564. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability was found in Shenzhen Coship WM3300 5.0.0.55. It has been rated as critical. Affected by this issue is an unknown code block of the file regx/wireless/wl_security_2G.asp of the component Password Reset. The manipulation as part of a POST Request leads to a credentials management vulnerability. Using CWE to declare the problem leads to CWE-255. Impacted is confidentiality, integrity, and availability. CVE summarizes:
An issue was discovered on Shenzhen Coship WM3300 WiFi Router 5.0.0.55 devices. The password reset functionality of the Wireless SSID doesn't require any type of authentication. By making a POST request to the regx/wireless/wl_security_2G.asp URI, the attacker can change the password of the Wi-FI network.
The bug was discovered 02/11/2019. The weakness was presented 05/07/2019. This vulnerability is handled as CVE-2019-7564 since 02/06/2019. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1552.
The vulnerability was handled as a non-public zero-day exploit for at least 85 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:regx/wireless/wl_security_2G.asp 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.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Credentials managementCWE: CWE-255
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
02/06/2019 🔍02/11/2019 🔍
05/07/2019 🔍
05/08/2019 🔍
09/15/2023 🔍
Sources
Advisory: 151595Status: Not defined
CVE: CVE-2019-7564 (🔍)
GCVE (CVE): GCVE-0-2019-7564
GCVE (VulDB): GCVE-100-134468
Entry
Created: 05/08/2019 07:33Updated: 09/15/2023 07:32
Changes: 05/08/2019 07:33 (56), 06/07/2020 18:12 (1), 09/15/2023 07:32 (4)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.