dbcve.org
Wnr2000v4 FirmwareOperating system · Netgear

CVE-2022-31937

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Netgear N300 wireless router wnr2000v4-V1.0.0.70 was discovered to contain a stack overflow via strcpy in uhttpd.

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 confidence

A stack-based buffer overflow vulnerability exists in the uhttpd web server on Netgear N300 WNR2000v4 routers (firmware V1.0.0.70) due to use of the unsafe strcpy function, which does not perform bounds checking before copying strings into fixed-size stack buffers. This allows remote attackers to overwrite return addresses and potentially achieve arbitrary code execution.

MitigationSince Netgear WNR2000v4 is an end-of-life device likely receiving no further security updates, users should replace the router or at minimum disable uhttpd and remote management interfaces, applying network segmentation to limit exposure.

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
Wnr2000v4 FirmwareOperating system
Affected:= 1.0.0.70

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your router model
    Check the label on the bottom of the router or log into the web interface to confirm the model is Netgear WNR2000v4 (N300)
    Affected if Model is not WNR2000v4 - you are not affected by this specific CVE
  2. Check the installed firmware version
    Log into the router web interface (typically at 192.168.1.1), go to Administration > Firmware Update or Router Status page, and note the firmware version displayed
    Affected if Firmware version is 1.0.0.70 - this is the only affected version listed for this CVE
  3. Verify uhttpd web server is enabled
    Access the router via telnet or SSH if enabled, then check running processes with 'ps' or look for uhttpd in /proc/version or /var/log/messages. Alternatively, attempt to access the router web interface on port 80 or 443
    Affected if The web interface is accessible and responds - uhttpd is running and the vulnerability is present
  4. Confirm remote management exposure
    Check router settings under Advanced > Remote Management or Administration > Remote Management to see if web interface access from WAN/internet is enabled
    Affected if Remote management is enabled and the router is directly accessible from the internet - attack surface is present

You are affected only if you have a WNR2000v4 router running firmware version 1.0.0.70 with the uhttpd web server enabled and preferably with remote management exposed to untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since Netgear WNR2000v4 is an end-of-life device likely receiving no further security updates, users should replace the router or at minimum disable uhttpd and remote management interfaces, applying network segmentation to limit exposure.

Recommended fix Moderate confidence

Latest WNR2000v4 firmware version available from NETGEAR support (newer than 1.0.0.70)

  1. 1. Visit the official NETGEAR support page for the WNR2000v4 router at www.netgear.com/support/
  2. 2. Navigate to the downloads/firmware section for WNR2000v4
  3. 3. Download the latest available firmware version (check for versions newer than 1.0.0.70)
  4. 4. Access the router's web management interface by entering 192.168.1.1 in a web browser
  5. 5. Log in with the router's admin credentials
  6. 6. Navigate to the Administration > Firmware Update section
  7. 7. Select the downloaded firmware file and initiate the update
  8. 8. Wait for the update to complete and the router to reboot
Caveat Standard firmware update - ensure power continuity during update; router will be temporarily unavailable

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

Fix this in Wnr2000v4 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31937 — 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-2022-31937 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