CommScope Ruckus IoT Controller up to 1.7.1.0 hard-coded password
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in CommScope Ruckus IoT Controller up to 1.7.1.0. It has been classified as problematic. This impacts an unknown function. This manipulation causes hard-coded password. The identification of this vulnerability is CVE-2021-33219. There is no exploit available.
Details
A vulnerability was found in CommScope Ruckus IoT Controller up to 1.7.1.0. It has been declared as problematic. Affected by this vulnerability is an unknown code block. 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, integrity, and availability.
The weakness was shared 07/08/2021. It is possible to read the advisory at seclists.org. This vulnerability is known as CVE-2021-33219. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1078.001 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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: Hard-coded passwordCWE: CWE-259 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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
05/20/2021 🔍07/08/2021 🔍
07/08/2021 🔍
07/10/2021 🔍
Sources
Advisory: seclists.orgStatus: Not defined
CVE: CVE-2021-33219 (🔍)
GCVE (CVE): GCVE-0-2021-33219
GCVE (VulDB): GCVE-100-178099
Entry
Created: 07/08/2021 09:54Updated: 07/10/2021 16:41
Changes: 07/08/2021 09:54 (34), 07/10/2021 16:41 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.