CVE-2021-29073
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCertain NETGEAR devices are affected by a stack-based buffer overflow by an authenticated user. This affects R8000P before 1.4.1.66, MK62 before 1.0.6.110, MR60 before 1.0.6.110, MS60 before 1.0.6.110, R7960P before 1.4.1.66, R7900P before 1.4.1.66, RAX15 before 1.0.2.82, RAX20 before 1.0.2.82, RAX45 before 1.0.2.72, RAX50 before 1.0.2.72, RAX75 before 1.0.3.106, RAX80 before 1.0.3.106, and RAX200 before 1.0.3.106.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStack-based buffer overflow vulnerability in multiple NETGEAR router firmware versions allows authenticated attackers to potentially execute arbitrary code via overflowing a stack-allocated buffer through the web management interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.4.1.66< 1.0.6.110< 1.0.6.110< 1.0.6.110< 1.4.1.66< 1.4.1.66< 1.0.2.82< 1.0.2.82CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your NETGEAR router modelLook at the device label on the router or log into the web management interface to confirm the exact model number (such as R8000p, Mk62, Mr60, Ms60, R7960p, R7900p, Rax15, or Rax20)Affected if The model is one of the eight affected models listed in the CVE
-
Check the installed firmware versionLog into the router web management interface (typically at 192.168.1.1 or routerlogin.net), navigate to the Administration or Firmware Update section, and locate the current firmware version numberAffected if The firmware version is lower than 1.4.1.66 for R8000p/R7960p/R7900p, lower than 1.0.6.110 for Mk62/Mr60/Ms60, or lower than 1.0.2.82 for Rax15/Rax20
-
Verify web management interface accessibilityConfirm whether the router web management interface is accessible from the WAN/internet side (check Port 80/443 forwarding rules or UPnP settings on the router)Affected if Remote administration is enabled and the web interface is reachable from outside the local network
-
Confirm authentication requirementsCheck if default or weak administrative credentials are in use for the router admin accountAffected if The default admin username (usually 'admin') is retained with a weak or default password, allowing authenticated attacker access
-
Determine if the specific vulnerable feature is in useThe vulnerability affects the web management interface processing. Determine if any HTTP-based management features or dynamic DNS services that interact with the web interface are enabledAffected if The web management interface is actively used and accepts authenticated HTTP requests
A user is affected if they own one of the eight listed NETGEAR models AND the firmware version is below the specified threshold AND an attacker could obtain valid admin credentials to access the web interface.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.0.2.821.0.6.1101.4.1.66
Update affected NETGEAR device firmware to the patched versions specified (1.4.1.66, 1.0.6.110, 1.0.2.82, 1.0.2.72, 1.0.3.106) and enforce strong administrative credentials to limit exploitation scope.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29073 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-29073 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data