dbcve.org
Wnr2000v4 FirmwareOperating system · Netgear

CVE-2022-37232

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-23
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 is vulnerable to Buffer Overflow via uhttpd. There is a stack overflow vulnerability caused by strcpy.

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 · moderate confidence

A stack-based buffer overflow vulnerability exists in the uhttpd web server component of Netgear N300 wireless router wnr2000v4 firmware V1.0.0.70. The vulnerability is caused by the unsafe use of strcpy() function, which does not perform bounds checking and allows an attacker to overflow a stack-allocated buffer, potentially leading to remote code execution.

MitigationApply available firmware updates from Netgear for the wnr2000v4 model; if no patch is available, consider disabling remote web management interfaces, restricting access to local network only, or replacing the end-of-life 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
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 the exact router model
    Check the device label or administrative interface for the model number WNR2000v4
    Affected if The device is not a Netgear WNR2000v4, then this specific CVE does not apply
  2. Check the installed firmware version
    Access the router web interface (typically at 192.168.1.1) and navigate to Administration > Firmware Update or check the status page for version 1.0.0.70, or use the command 'nvram get firmware_version' via telnet/shell if available
    Affected if The firmware version is exactly 1.0.0.70 - only this specific version is listed as affected
  3. Verify the uhttpd web server component is active
    Check if the router web interface is accessible on ports 80 or 443 by attempting to reach the device IP from a browser
    Affected if The web interface is accessible and the router is running, meaning the vulnerable uhttpd component is active
  4. Confirm remote management is enabled
    In the router web interface, check Advanced > Remote Management or similar settings to see if web management access is permitted from external IPs
    Affected if Remote web management is enabled, allowing potential attackers on the internet to reach the vulnerable uhttpd service

You are affected only if you have an exact WNR2000v4 device running firmware version 1.0.0.70 with the uhttpd web server accessible (especially if remote management is enabled).

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

Apply available firmware updates from Netgear for the wnr2000v4 model; if no patch is available, consider disabling remote web management interfaces, restricting access to local network only, or replacing the end-of-life device.

Recommended fix Moderate confidence

Latest available Wnr2000v4 firmware from Netgear support site

  1. 1. Access the Netgear Wnr2000v4 router web interface by navigating to the router's IP address (typically 192.168.1.1)
  2. 2. Log in with the router's administrator credentials
  3. 3. Navigate to the Administration or Firmware Update section
  4. 4. Check for available firmware updates. If an update is available, download and install it
  5. 5. Alternatively, visit the official Netgear support page at www.netgear.com and search for the Wnr2000v4 model
  6. 6. Download the latest available firmware version from Netgear's official support site
  7. 7. In the router's Administration section, use the manual firmware update option to upload and install the downloaded firmware file
  8. 8. After the update completes, verify the new firmware version in the router settings

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

Fix this in Wnr2000v4 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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