dbcve.org
R6400v2 FirmwareOperating system · Netgear

CVE-2021-45643

MEDIUM · 6.5 CVSS v3.1 Published 2021-12-26
Fix available
A fix is available. Upgrade to 1.0.0.58 / 1.0.4.118 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click Patch available

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 · unedited
Certain NETGEAR devices are affected by incorrect configuration of security settings. This affects R6400v2 before 1.0.4.118, R6700v3 before 1.0.4.118, and XR1000 before 1.0.0.58.

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

A detailed technical summary for this CVE is being prepared.

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
R6400v2 FirmwareOperating system
Affected:< 1.0.4.118
R6700v3 FirmwareOperating system
Affected:< 1.0.4.118
Xr1000 FirmwareOperating system
Affected:< 1.0.0.58

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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 · scoped
Upgrade available Upgrade to 1.0.0.58 / 1.0.4.118 or later
Fixed in 1.0.0.581.0.4.118
Vendor patch kb.netgear.com →
Recommended fix High confidence

R6400v2: upgrade to 1.0.4.118 or later | R6700v3: upgrade to 1.0.4.118 or later | Xr1000: upgrade to 1.0.0.58 or later

  1. Identify your NETGEAR router model (R6400v2, R6700v3, or Xr1000)
  2. Navigate to the NETGEAR support website and download the firmware update: R6400v2 or R6700v3 to version 1.0.4.118, Xr1000 to version 1.0.0.58
  3. Log in to the router's web management interface (typically at routerlogin.net or 192.168.1.1)
  4. Go to the Administration > Firmware Update section
  5. Click Browse or Choose File and select the downloaded firmware file
  6. Click Upload or Update to begin the firmware upgrade process
  7. Wait for the upload to complete and do not power off the router during the upgrade
  8. After the router reboots, log back in and verify the firmware version under Administration > Router Status to confirm the update was successful
Caveat Firmware upgrades may reset some custom settings; reconfigure any personalized settings after upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-45643 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-45643 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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