CVE-2021-45610: Certain NETGEAR devices are affected by a buffer overflow by an unauthenticated attacker.
Noroxi assessment
Priority: Monitor (action score 39/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: 1.4% (FIRST EPSS); higher than 74.6% of all records.
- Anyone who can reach it over the internet 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.
Low priority for now. 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
Certain NETGEAR devices are affected by a buffer overflow by an unauthenticated attacker. This affects D6220 before 1.0.0.66, D6400 before 1.0.0.100, D7000v2 before 1.0.0.66, D8500 before 1.0.3.58, DC112A before 1.0.0.52, DGN2200v4 before 1.0.0.118, EAX80 before 1.0.1.64, R6250 before 1.0.4.48, R7000 before 1.0.11.110, R7100LG before 1.0.0.72, R7900 before 1.0.4.30, R7960P before 1.4.1.64, R8000 before 1.0.4.62, RAX200 before 1.0.3.106, RS400 before 1.5.1.80, XR300 before 1.0.3.68, R6400v2 before 1.0.4.106, R7000P before 1.3.2.132, R8000P before 1.4.1.64, RAX20 before 1.0.2.82, RAX45 before 1.0.2.82, RAX80 before 1.0.3.106, R6700v3 before 1.0.4.106, R6900P before 1.3.2.132, R7900P before 1.4.1.64, RAX15 before 1.0.2.82, RAX50 before 1.0.2.82, and RAX75 before 1.0.3.106.
- Published
- Dec 25, 2021
- Updated
- Jun 17, 2026
- EPSS
- 1.4% · 74th percentile
- CWE
- CWE-120
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
CNA vs NVD score
- NVD
- 9.8
- CNA · mitre
- 9.6
- 0.2 point gap
CVSS:3.1/AC:L/AV:A/A:H/C:H/I:H/PR:N/S:C/UI:N
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 | d6220 firmware | cpe:2.3:o:netgear:d6220_firmware |
| netgear | d6220 | cpe:2.3:h:netgear:d6220 |
| netgear | d6400 firmware | cpe:2.3:o:netgear:d6400_firmware |
| netgear | d6400 | cpe:2.3:h:netgear:d6400 |
| netgear | d7000v2 firmware | cpe:2.3:o:netgear:d7000v2_firmware |
| netgear | d7000v2 | cpe:2.3:h:netgear:d7000v2 |
| netgear | d8500 firmware | cpe:2.3:o:netgear:d8500_firmware |
| netgear | d8500 | cpe:2.3:h:netgear:d8500 |
| netgear | dc112a firmware | cpe:2.3:o:netgear:dc112a_firmware |
| netgear | dc112a | cpe:2.3:h:netgear:dc112a |
| netgear | dgn2200v4 firmware | cpe:2.3:o:netgear:dgn2200v4_firmware |
| netgear | dgn2200v4 | cpe:2.3:h:netgear:dgn2200v4 |
and 44 more
Affected versions
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.66
- netgear d6400 firmwarebefore 1.0.0.100
- netgear d7000v2 firmwarebefore 1.0.0.66
- netgear d8500 firmwarebefore 1.0.3.58
- netgear dc112a firmwarebefore 1.0.0.52
- netgear dgn2200v4 firmwarebefore 1.0.0.118
- netgear eax80 firmwarebefore 1.0.1.64
- netgear r6250 firmwarebefore 1.0.4.48
+12 more rows
- netgear r6400v2 firmwarebefore 1.0.4.106
- netgear r6700v3 firmwarebefore 1.0.4.106
- netgear r6900p firmwarebefore 1.3.2.132
- netgear r7000 firmwarebefore 1.0.11.110
- netgear r7000p firmwarebefore 1.3.2.132
- netgear r7100lg firmwarebefore 1.0.0.72
- netgear r7900 firmwarebefore 1.0.4.30
- netgear r7900p firmwarebefore 1.4.1.64
- netgear r7960p firmwarebefore 1.4.1.64
- netgear r8000 firmwarebefore 1.0.4.62
- netgear r8000p firmwarebefore 1.4.1.64
- netgear rax15 firmwarebefore 1.0.2.82
Same product
netgear: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-6277NETGEAR R6250 before 1.0.4.6.Beta, R6400 before 1.0.1.18.Beta, R6700 before 1.0.1.14.Beta, R6900, R7000 before 1.0.7.6.Beta, R7100LG before…KEV95Now
- CVE-2021-45638Certain NETGEAR devices are affected by a stack-based buffer overflow by an unauthenticated attacker.39Monitor
- CVE-2021-38516Certain NETGEAR devices are affected by lack of access control at the function level.39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-27239Mar 29, 2021 · This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of NETGEAR R6400 and R6700…35Monitor
- ← EarlierCVE-2021-45531Dec 25, 2021 · NETGEAR D6220 devices before 1.0.0.76 are affected by command injection by an authenticated user.35Monitor
- Later →CVE-2023-33533Jun 6, 2023 · Netgear D6220 with Firmware Version 1.0.0.80, D8500 with Firmware Version 1.0.3.60, R6700 with Firmware Version 1.0.2.26, and R6900 with…36Monitor
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet 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
- Network
- 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:N/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
Vendor advisories and official records. Exploit/PoC links are deliberately left out.