CVE-2022-27643: This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of NETGEAR R6700v3…
Noroxi assessment
Priority: Plan (action score 43/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 25.4% (FIRST EPSS); higher than 97.9% of all records.
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
This vulnerability allows network-adjacent attackers to execute arbitrary code 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 handling of SOAP requests. When parsing the SOAPAction header, the process does not properly validate the length of user-supplied data prior to copying it to a buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-15692.
- Published
- Mar 29, 2023
- Updated
- Jun 17, 2026
- EPSS
- 25.4% · 97th percentile
- CWE
- CWE-120
Report tools
Action score
43
Add it to your regular patch cycle.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 8 / 30 · 25.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.8
- CNA · zdi
- 8.8
- agree
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| netgear | r6400 firmware | cpe:2.3:o:netgear:r6400_firmware |
| netgear | r6400 | cpe:2.3:h:netgear:r6400 |
| netgear | r6700 firmware | cpe:2.3:o:netgear:r6700_firmware |
| netgear | r6700 | cpe:2.3:h:netgear:r6700 |
| netgear | r6900p firmware | cpe:2.3:o:netgear:r6900p_firmware |
| netgear | r6900p | cpe:2.3:h:netgear:r6900p |
| netgear | r7000 firmware | cpe:2.3:o:netgear:r7000_firmware |
| netgear | r7000 | cpe:2.3:h:netgear:r7000 |
| netgear | r7000p firmware | cpe:2.3:o:netgear:r7000p_firmware |
| netgear | r7000p | cpe:2.3:h:netgear:r7000p |
| netgear | r7850 firmware | cpe:2.3:o:netgear:r7850_firmware |
| netgear | r7850 | cpe:2.3:h:netgear:r7850 |
and 42 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (zdi). Independent of NVD's CPE analysis and usually ahead of it.
NETGEAR R6700v3
- 1.0.4.120_10.0.91affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netgear d6220 firmwarebefore 1.0.0.80
- netgear d6400 firmwarebefore 1.0.0.114
- netgear d7000v2 firmwarebefore 1.0.0.80
- netgear dc112a firmwarebefore 1.0.0.64
- netgear ex3700 firmwarebefore 1.0.0.96
- netgear ex3800 firmwarebefore 1.0.0.96
- netgear ex6120 firmwarebefore 1.0.0.68
- netgear ex6130 firmwarebefore 1.0.0.48
- netgear r6400 firmwarebefore 1.0.1.78
- netgear r6400 firmwarebefore 1.0.4.126
- netgear r6700 firmwarebefore 1.0.4.126
- netgear r6900p firmwarebefore 1.3.3.148
- netgear r7000 firmwarebefore 1.0.11.134
- netgear r7000p firmwarebefore 1.3.3.148
- netgear r7100lg firmwarebefore 1.0.0.76
- netgear r7850 firmwarebefore 1.0.5.84
- netgear r7900p firmwarebefore 1.4.3.88
- netgear r7960p firmwarebefore 1.4.3.88
- netgear r8000 firmwarebefore 1.0.4.84
- netgear r8000p firmwarebefore 1.4.3.88
Same product
netgear: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-11789Certain NETGEAR devices are affected by command injection by an unauthenticated attacker.40Plan
- CVE-2022-27646This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of NETGEAR R6700v3…35Monitor
- CVE-2022-27644This vulnerability allows network-adjacent attackers to compromise the integrity of downloaded information on affected installations of…35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-45605Dec 25, 2021 · Certain NETGEAR devices are affected by a stack-based buffer overflow by an authenticated user.35Monitor
- ← EarlierCVE-2021-45606Dec 25, 2021 · Certain NETGEAR devices are affected by a stack-based buffer overflow by an authenticated user.35Monitor
- ← EarlierCVE-2021-45655Dec 25, 2021 · NETGEAR R6400 devices before 1.0.1.70 are affected by server-side injection.27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Stephen FewerRapid7
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.