CVE-2022-46423
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 · uneditedAn exploitable firmware modification vulnerability was discovered on the Netgear WNR2000v1 router. An attacker can conduct a MITM (Man-in-the-Middle) attack to modify the user-uploaded firmware image and bypass the CRC check, allowing attackers to execute arbitrary code or cause a Denial of Service (DoS). This affects v1.2.3.7 and earlier.
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 confidenceThe Netgear WNR2000v1 router firmware update mechanism fails to properly validate firmware integrity when users upload firmware images. An attacker positioned as a MITM can intercept the firmware upload, modify the image to bypass the CRC check, and flash malicious firmware, achieving arbitrary code execution or causing denial of service.
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.2.3.7CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Confirm device model is Netgear WNR2000Check the router label on the device or log into the router admin interface (usually at 192.168.1.1) and look for the model number in the status or settings pagesAffected if The device is NOT a Netgear WNR2000 (variant or different model)
-
Check installed firmware versionLog into the router web admin interface, navigate to Router Status or Administration section, and locate the firmware version field. Compare this version number against 1.2.3.7Affected if The installed firmware version is 1.2.3.7 or lower (any version <= 1.2.3.7)
-
Verify firmware update functionality is accessibleCheck if the router admin web interface includes a Firmware Update or Router Upgrade option under Administration or Maintenance settings. Note whether this interface is reachable over HTTP (port 80) vs HTTPSAffected if The firmware update web interface is exposed and accessible (typically on HTTP by default)
-
Assess network exposure during firmware updatesDetermine how firmware updates are performed: check if the router downloads firmware from the internet directly, or if uploads are done from a local computer. Note whether the network path between the computer and router is trustedAffected if Firmware updates are performed over an untrusted network or the router admin interface is accessible from untrusted networks (WAN)
-
Check for CRC/integrity validation behaviorInspect the router firmware update process by attempting a test firmware upload through the admin interface. Note whether the router accepts firmware files without explicit cryptographic verification promptsAffected if The router accepts and attempts to flash firmware without requiring manual verification of checksums provided by Netgear
You are affected if your Netgear WNR2000 device runs firmware version 1.2.3.7 or lower and the firmware update feature is accessible (particularly over untrusted networks or without manual checksum verification).
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 dataAvoid updating firmware over untrusted networks; verify firmware authenticity using official Netgear checksums; apply any vendor firmware updates if available.
- Consultation4.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46423 — 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-2022-46423 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