Netgear R6700 1.0.4.84_10.0.58 Firmware Update risky encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Netgear R6700 1.0.4.84_10.0.58. Affected by this vulnerability is an unknown functionality of the component Firmware Update Handler. Performing a manipulation results in risky encryption. This vulnerability was named CVE-2020-10927. The attack needs to be approached within the local network. There is no available exploit.
Details
A vulnerability classified as critical has been found in Netgear R6700 1.0.4.84_10.0.58 (Wireless LAN Software). This affects an unknown code of the component Firmware Update Handler. The manipulation with an unknown input leads to a risky encryption vulnerability. CWE is classifying the issue as CWE-327. The product uses a broken or risky cryptographic algorithm or protocol. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of NETGEAR R6700 V1.0.4.84_10.0.58 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the encryption of firmware update images. The issue results from the use of an inappropriate encryption algorithm. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of root. Was ZDI-CAN-9649.
The weakness was presented 07/28/2020 (Website). The advisory is shared at zerodayinitiative.com. This vulnerability is uniquely identified as CVE-2020-10927 since 03/24/2020. The attack needs to be initiated within the local network. No form of authentication is needed for exploitation. 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 07/29/2020). MITRE ATT&CK project uses the attack technique T1600 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-159096, VDB-159095, VDB-159094 and VDB-159092 for similar entries. 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.netgear.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 8.2
VulDB Base Score: 8.8
VulDB Temp Score: 8.8
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: 🔍
Exploiting
Class: Risky encryptionCWE: CWE-327 / CWE-310
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
03/24/2020 🔍07/28/2020 🔍
07/29/2020 🔍
11/06/2020 🔍
Sources
Vendor: netgear.comAdvisory: zerodayinitiative.com
Status: Not defined
CVE: CVE-2020-10927 (🔍)
GCVE (CVE): GCVE-0-2020-10927
GCVE (VulDB): GCVE-100-159093
See also: 🔍
Entry
Created: 07/29/2020 19:56Updated: 11/06/2020 09:25
Changes: 07/29/2020 19:56 (39), 07/29/2020 20:01 (12), 11/06/2020 09:25 (1)
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.