ZyXEL CloudCNM SecuManager 3.1.0/3.1.1 Axiros Account hard-coded password
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in ZyXEL CloudCNM SecuManager 3.1.0/3.1.1. This vulnerability affects unknown code of the component Axiros Account. This manipulation causes hard-coded password. This vulnerability appears as CVE-2020-15347. There is no available exploit.
Details
A vulnerability classified as problematic was found in ZyXEL CloudCNM SecuManager 3.1.0/3.1.1 (Cloud Software). Affected by this vulnerability is an unknown code of the component Axiros Account. The manipulation with an unknown input leads to a hard-coded password vulnerability. The CWE definition for the vulnerability is CWE-259. The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components. As an impact it is known to affect confidentiality. The summary by CVE is:
Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has the q6xV4aW8bQ4cfD-b password for the axiros account.
The weakness was presented 09/29/2022. The advisory is shared at pierrekim.github.io. This vulnerability is known as CVE-2020-15347 since 06/26/2020. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/25/2022). MITRE ATT&CK project uses the attack technique T1078.001 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.zyxel.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 7.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: 🔍
Exploiting
Class: Hard-coded passwordCWE: CWE-259 / CWE-255
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
06/26/2020 🔍09/29/2022 🔍
09/29/2022 🔍
10/25/2022 🔍
Sources
Vendor: zyxel.comAdvisory: pierrekim.github.io
Status: Not defined
CVE: CVE-2020-15347 (🔍)
GCVE (CVE): GCVE-0-2020-15347
GCVE (VulDB): GCVE-100-209773
Entry
Created: 09/29/2022 09:05Updated: 10/25/2022 10:06
Changes: 09/29/2022 09:05 (38), 10/25/2022 10:06 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.