R6700v3: Stack-based Buffer Overflow
CVE-2022-27646 is a high-severity stack-based buffer overflow 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 1.43% chance of exploitation within 30 days, higher than 73% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update R6400 Firmware to 1.0.4.126 or a later version.
- Update R6700 Firmware to 1.0.4.126 or a later version.
- Update R6900p Firmware to 1.3.3.148 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 | R6400 Firmware | before 1.0.4.126 | 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 | 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 | Rax200 Firmware | before 1.0.6.138 | 1.0.6.138 |
| NETGEAR | Rax75 Firmware | before 1.0.6.138 | 1.0.6.138 |
| NETGEAR | Rax80 Firmware | before 1.0.6.138 | 1.0.6.138 |
| NETGEAR | Rs400 Firmware | before 1.5.1.86 | 1.5.1.86 |
| NETGEAR | Cbr40 Firmware | before 2.5.0.28 | 2.5.0.28 |
| NETGEAR | Lbr1020 Firmware | before 2.7.4.2 | 2.7.4.2 |
| NETGEAR | Lbr20 Firmware | before 2.7.4.2 | 2.7.4.2 |
| NETGEAR | Rbr10 Firmware | before 2.7.4.24 | 2.7.4.24 |
| NETGEAR | Rbr20 Firmware | before 2.7.4.24 | 2.7.4.24 |
| NETGEAR | Rbr40 Firmware | before 2.7.4.24 | 2.7.4.24 |
| NETGEAR | Rbr50 Firmware | before 2.7.4.24 | 2.7.4.24 |
| NETGEAR | Rbs10 Firmware | before 2.7.4.24 | 2.7.4.24 |
| NETGEAR | Rbs20 Firmware | before 2.7.4.24 | 2.7.4.24 |
| NETGEAR | Rbs40 Firmware | before 2.7.4.24 | 2.7.4.24 |
| NETGEAR | Rbs50 Firmware | before 2.7.4.24 | 2.7.4.24 |
Version data comes from the organisation that assigned the CVE. 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 | 8.0 | High | CNA (trendmicro.com) |
Official description
This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of NETGEAR R6700v3 1.0.4.120_10.0.91 routers. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the circled daemon. A crafted circleinfo.txt file can trigger an overflow of a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-15879.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Stack-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the stack.
How developers prevent this class of flaw
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Implement and perform bounds checking on input.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- zerodayinitiative.com/advisories/ZDI-22-523/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 Stack-based Buffer Overflow vulnerabilities
- 8.8 High severity
- 8.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.