Motorola CX2 CX 1.0.2 Build 20190508 Rel.97360n HNAP1/GetMultipleHNAPs missing authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Motorola CX2 CX 1.0.2 Build 20190508 Rel.97360n. This issue affects the function GetStationSettings/GetWebsiteFilterSettings/GetNetworkSettings of the file HNAP1/GetMultipleHNAPs. Performing a manipulation results in missing authentication.
This vulnerability is reported as CVE-2020-21936. No exploit exists.
Details
A vulnerability, which was classified as critical, was found in Motorola CX2 CX 1.0.2 Build 20190508 Rel.97360n. This affects the function GetStationSettings/GetWebsiteFilterSettings/GetNetworkSettings of the file HNAP1/GetMultipleHNAPs. The manipulation with an unknown input leads to a missing authentication vulnerability. CWE is classifying the issue as CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. This is going to have an impact on confidentiality.
The weakness was disclosed 07/22/2021. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2020-21936. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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: Missing authenticationCWE: CWE-306 / CWE-287
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
08/13/2020 🔍07/22/2021 🔍
07/22/2021 🔍
07/26/2021 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2020-21936 (🔍)
GCVE (CVE): GCVE-0-2020-21936
GCVE (VulDB): GCVE-100-179337
Entry
Created: 07/22/2021 05:51Updated: 07/26/2021 09:53
Changes: 07/22/2021 05:51 (37), 07/26/2021 09:53 (2)
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.