CVE-2021-29069
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 command injection by an authenticated user. This affects XR450 before 2.3.2.114, XR500 before 2.3.2.114, and WNR2000v5 before 1.0.0.76.
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 confidenceAuthenticated command injection vulnerability in NETGEAR XR450, XR500, and WNR2000v5 routers allows attackers with valid credentials to execute arbitrary commands on the underlying operating system. The flaw exists in the firmware versions prior to 2.3.2.114 for XR450/XR500 and 1.0.0.76 for WNR2000v5.
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.3.2.114< 2.3.2.114< 1.0.0.76CVSS 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 router modelAccess the router web interface (typically at 192.168.1.1) and check the device model name on the status or maintenance page, or physically inspect the device labelAffected if Model is XR450, XR500, or WNR2000v5
-
Check XR450/XR500 firmware versionIn the router web interface, go to Administration > Firmware Update or Advanced > Administration > Router Status. Note the firmware version displayed (example format: 2.3.2.104)Affected if Version is lower than 2.3.2.114 (e.g., 2.3.2.100, 2.3.0.26)
-
Check WNR2000v5 firmware versionIn the router web interface, go to Router Status or Administration > Firmware Upgrade. Note the firmware version displayed (example format: 1.0.0.60)Affected if Version is lower than 1.0.0.76 (e.g., 1.0.0.50)
-
Verify remote management is accessibleCheck if the router admin interface is reachable from external networks. In web interface, go to Advanced > Administration > Remote Management. If enabled, the router can be accessed via WAN IP on port 8080 or similarAffected if Remote management is enabled and the router is internet-facing, allowing authenticated attackers to reach the injection point
You are affected if you own an XR450, XR500, or WNR2000v5 router with firmware version below 2.3.2.114 (XR450/XR500) or below 1.0.0.76 (WNR2000v5), especially if remote management is enabled
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.0.762.3.2.114
Update affected NETGEAR router firmware to version 2.3.2.114 (XR450/XR500) or 1.0.0.76 (WNR2000v5). If updates are unavailable, restrict administrative interface access to trusted networks only and monitor for unauthorized access.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29069 — 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-29069 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