R6700v3: Incorrect Authorization
CVE-2022-27642 is a high-severity incorrect authorization vulnerability in R6700v3 from NETGEAR, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. Affected R6700v3 versions: 1.0.4.120_10.0.91. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.88% chance of exploitation within 30 days, higher than 60% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Cax80 Firmware to 2.1.3.7 or a later version.
- Update Lax20 Firmware to 1.1.6.34 or a later version.
- Update Mr60 Firmware to 1.1.6.124 or a later version.
- Read the advisory on kb.netgear.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| NETGEAR | R6700v3 | 1.0.4.120_10.0.91 | Not stated |
| NETGEAR | Cax80 Firmware | before 2.1.3.7 | 2.1.3.7 |
| NETGEAR | Lax20 Firmware | before 1.1.6.34 | 1.1.6.34 |
| NETGEAR | Mr60 Firmware | before 1.1.6.124 | 1.1.6.124 |
| NETGEAR | Mr80 Firmware | before 1.1.6.14 | 1.1.6.14 |
| NETGEAR | Ms60 Firmware | before 1.1.6.124 | 1.1.6.124 |
| NETGEAR | Ms80 Firmware | before 1.1.6.14 | 1.1.6.14 |
| NETGEAR | R6400 Firmware | before 1.0.1.78; before 1.0.4.126 | 1.0.1.78, 1.0.4.126 |
| NETGEAR | R6700 Firmware | before 1.0.4.126 | 1.0.4.126 |
| NETGEAR | R6900p Firmware | before 1.3.3.148 | 1.3.3.148 |
| NETGEAR | R7000 Firmware | before 1.0.11.134 | 1.0.11.134 |
| NETGEAR | R7000p Firmware | before 1.3.3.148 | 1.3.3.148 |
| NETGEAR | R7850 Firmware | before 1.0.5.84 | 1.0.5.84 |
| NETGEAR | R7900p Firmware | before 1.4.3.88 | 1.4.3.88 |
| NETGEAR | R7960p Firmware | before 1.4.3.88 | 1.4.3.88 |
| NETGEAR | R8000 Firmware | before 1.0.4.84 | 1.0.4.84 |
| NETGEAR | R8000p Firmware | before 1.4.3.88 | 1.4.3.88 |
| NETGEAR | R8500 Firmware | before 1.0.2.158 | 1.0.2.158 |
| NETGEAR | Rax15 Firmware | before 1.0.10.110 | 1.0.10.110 |
| NETGEAR | Rax20 Firmware | before 1.0.10.110 | 1.0.10.110 |
| NETGEAR | Rax200 Firmware | before 1.0.6.138 | 1.0.6.138 |
| NETGEAR | Rax35 Firmware | before 1.0.10.110 | 1.0.10.110 |
| NETGEAR | Rax38 Firmware | before 1.0.10.110 | 1.0.10.110 |
| NETGEAR | Rax40 Firmware | before 1.0.10.110 | 1.0.10.110 |
| NETGEAR | Rax42 Firmware | before 1.0.10.110 | 1.0.10.110 |
Version data comes from the organisation that assigned the CVE; 9 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | NVD |
| CVSS 3.0 | 6.3 | Medium | CNA (trendmicro.com) |
Official description
This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of NETGEAR R6700v3 1.0.4.120_10.0.91 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the httpd service. The issue results from incorrect string matching logic when accessing protected pages. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of root. Was ZDI-CAN-15854.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- zerodayinitiative.com/advisories/ZDI-22-518/Third Party Advisory, VDB Entry
Other vulnerabilities in R6700v3
- 8.0 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Recent Incorrect Authorization vulnerabilities
- 8.8 High severity
- 7.5 High severity
- 8.1 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.