CVE-2021-45619
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 unauthenticated attacker. This affects EX6200v2 before 1.0.1.86, EX6250 before 1.0.0.134, EX7700 before 1.0.0.216, EX8000 before 1.0.1.232, LBR1020 before 2.6.3.58, LBR20 before 2.6.3.50, R7800 before 1.0.2.80, R8900 before 1.0.5.26, R9000 before 1.0.5.26, RBS50Y before 2.7.3.22, WNR2000v5 before 1.0.0.76, XR700 before 1.0.1.36, EX6150v2 before 1.0.1.98, EX7300 before 1.0.2.158, EX7320 before 1.0.0.134, RAX10 before 1.0.2.88, RAX120 before 1.2.0.16, RAX70 before 1.0.2.88, EX6100v2 before 1.0.1.98, EX6400 before 1.0.2.158, EX7300v2 before 1.0.0.134, R6700AX before 1.0.2.88, RAX120v2 before 1.2.0.16, RAX78 before 1.0.2.88, EX6410 before 1.0.0.134, RBR10 before 2.7.3.22, RBR20 before 2.7.3.22, RBR350 before 4.3.4.7, RBR40 before 2.7.3.22, RBR50 before 2.7.3.22, EX6420 before 1.0.0.134, RBS10 before 2.7.3.22, RBS20 before 2.7.3.22, RBS350 before 4.3.4.7, RBS40 before 2.7.3.22, RBS50 before 2.7.3.22, EX6400v2 before 1.0.0.134, RBK12 before 2.7.3.22, RBK20 before 2.7.3.22, RBK352 before 4.3.4.7, RBK40 before 2.7.3.22, and RBK50 before 2.7.3.22.
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 confidenceUnauthenticated command injection vulnerability in the web management interface of NETGEAR router and mesh WiFi devices. An attacker can send specially crafted HTTP requests containing malicious OS commands that get executed with elevated privileges on the device, effectively giving the attacker full control over the affected device.
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.0.0.134< 1.0.0.216< 1.0.1.232< 2.6.3.58< 2.6.3.50< 1.0.2.80< 1.0.5.26< 2.7.3.22CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 the NETGEAR device modelCheck the device label on the physical device, or log into the router web interface and look at the status or administration page to confirm the exact model number (e.g., Ex6250, Ex7700, R7800, etc.)Affected if The device model matches one of the affected models: Ex6250, Ex7700, Ex8000, Lbr1020, Lbr20, R7800, R8900, or Rbs50y
-
Check the installed firmware versionLog into the router web management interface and navigate to the Administration or Firmware Update section to view the current firmware version, or use the NETGEAR router web UI status pageAffected if The firmware version is lower than the threshold for your model: Ex6250 < 1.0.0.134, Ex7700 < 1.0.0.216, Ex8000 < 1.0.1.232, Lbr1020 < 2.6.3.58, Lbr20 < 2.6.3.50, R7800 < 1.0.2.80, R8900 < 1.0.5.26, Rbs50y < 2.7.3.22
-
Verify if the web management interface is accessibleAttempt to access the router web interface from the network by navigating to the default gateway IP (commonly 192.168.1.1) over HTTP/HTTPS, or scan the external IP for open HTTP/HTTPS ports if remote management is enabledAffected if The web management interface is reachable from the network (either locally or remotely if remote management is enabled)
-
Confirm remote management is enabled (if applicable)Log into the router web interface and check the Administration or Remote Management settings to see if remote access via HTTP/HTTPS is enabledAffected if Remote web management is enabled and the interface is exposed to the internet
You are affected if you have a listed NETGEAR device model running firmware below the version threshold AND the web management interface is accessible on your network.
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.
dbcve · scoped1.0.0.1341.0.0.2161.0.1.232
Apply the vendor-supplied firmware updates to the specified version thresholds for each affected device model. If firmware updates are unavailable, disable remote web management interfaces and restrict local access.
EX6250: 1.0.0.134 | EX7700: 1.0.0.216 | EX8000: 1.0.1.232 | LBR1020: 2.6.3.58 | LBR20: 2.6.3.50 | R7800: 1.0.2.80 | R8900: 1.0.5.26 | RBS50Y: 2.7.3.22
- Identify your exact NETGEAR device model number (e.g., EX6250, R7800, RBS50Y)
- Navigate to the NETGEAR support website (kb.netgear.com) or download center
- Enter your device model to find the latest firmware
- Download the firmware file for your specific model
- Access your device's web administration interface using a browser
- Locate the Firmware Update or Administration section in the router GUI
- Upload the downloaded firmware file and initiate the update
- Wait for the update to complete - do not power off the device
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45619 — 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-45619 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