CVE-2021-29075
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 RBW30 before 2.6.2.2, RBK852 before 3.2.17.12, RBK852 before 3.2.17.12, RBK852 before 3.2.17.12, RBR850 before 3.2.17.12, RBS850 before 3.2.17.12, RBK752 before 3.2.17.12, RBK753 before 3.2.17.12, RBK753S before 3.2.17.12, RBK754 before 3.2.17.12, RBR750 before 3.2.17.12, and RBS750 before 3.2.17.12.
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 NETGEAR mesh WiFi devices (RBW30, RBK852, RBR850, RBS850, RBK752, RBK753, RBK753S, RBK754, RBR750, RBS750) that can be exploited by an authenticated user, allowing potential code execution or device compromise.
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< 2.6.2.2< 3.2.17.12< 3.2.17.12< 3.2.17.12< 3.2.17.12< 3.2.17.12< 3.2.17.12< 3.2.17.12CVSS 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 mesh device modelCheck the label on the device or log into the NETGEAR Orbi web interface to view the device model name under Administration > Device InformationAffected if The device model is RBW30, RBK852, RBK853, RBK854, RBR850, RBS850, RBK752, or RBK753 (or one of the variants listed in the CVE summary)
-
Locate the firmware version in the admin panelLog into the NETGEAR Orbi web interface at the router's IP address, then go to Administration > Firmware Update or Administration > Device Information to view the current firmware versionAffected if The displayed firmware version is lower than the thresholds (less than 2.6.2.2 for RBW30, or less than 3.2.17.12 for all other affected models)
-
Confirm the exact firmware version numberRecord the full firmware version string shown in the web interface under Administration > Device Information, paying attention to all numeric octetsAffected if The version shown is for example 2.6.1.10 (RBW30) or 3.2.16.8 (others), which are below the fixed versions 2.6.2.2 and 3.2.17.12 respectively
-
Verify if remote management or cloud access is enabledIn the web interface under Settings > Internet Setup or Advanced > Remote Management, check if remote access features are enabled that could allow an authenticated attacker to reach the vulnerable codeAffected if Remote management or NETGEAR cloud access is enabled, expanding the attack surface for an authenticated attacker to exploit the buffer overflow
Your device is affected if it is one of the listed models running firmware version 2.6.2.2 or lower for RBW30, or 3.2.17.12 or lower for all other listed models.
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 data2.6.2.23.2.17.12
Update firmware to version 2.6.2.2 (RBW30) or 3.2.17.12 (all other affected models) as provided by NETGEAR to remediate the vulnerability.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29075 — 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-29075 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