CVE-2021-34983
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 · uneditedNETGEAR Multiple Routers httpd Missing Authentication for Critical Function Information Disclosure Vulnerability. This vulnerability allows network-adjacent attackers to disclose sensitive information on affected installations of multiple NETGEAR routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the httpd service, which listens on TCP port 80 by default. The issue results from the lack of authentication prior to allowing access to system configuration information. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-13708.
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 confidenceThe httpd service on NETGEAR routers (TCP port 80) lacks authentication checks before providing access to system configuration data. This allows remote, unauthenticated attackers on the adjacent network to retrieve stored credentials and other sensitive system information.
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.64< 1.0.3.68< 1.0.0.76< 1.0.0.108< 1.0.0.76< 1.0.0.126< 1.0.0.80< 1.0.0.62CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 router modelLog into the router web interface (typically 192.168.1.1) and navigate to the Administration or Status page to view the device model name, or inspect the device label on the router chassis.Affected if The model is one of: Xr1000, Xr300, D6220, D6400, D7000v2, Dgn2200v4, V6510 1fxaus, or Dc112a.
-
Check the installed firmware versionIn the router web interface, go to Administration > Firmware Update or Router Status page to view the current firmware version.Affected if The firmware version is below the threshold for your model: Xr1000 < 1.0.0.64, Xr300 < 1.0.3.68, D6220 < 1.0.0.76, D6400 < 1.0.0.108, D7000v2 < 1.0.0.76, Dgn2200v4 < 1.0.0.126, V6510 1fxaus < 1.0.0.80, Dc112a < 1.0.0.62.
-
Verify HTTP service is accessible on port 80Use a web browser or curl command to access http://[router-ip]/ (port 80) from a client on the same network. Confirm the page loads.Affected if The router responds on port 80 without requiring authentication.
-
Test for unauthenticated access to sensitive endpointsAttempt to access common configuration endpoints without logging in, such as http://[router-ip]/cfg or similar paths that may expose system configuration data. Use curl or browser to check if sensitive information is returned without authentication prompts.Affected if The router returns configuration data, credentials, or sensitive system information without requiring any login credentials.
You are affected if your NETGEAR router model matches one of the eight listed models, your firmware version is below the specified threshold, and the httpd service on port 80 is exposed and returns sensitive data without authentication.
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.621.0.0.641.0.0.76
Restrict access to the router's management interface (port 80/443) from untrusted networks, apply available NETGEAR firmware patches, and rotate exposed credentials immediately.
Update to firmware version 1.0.0.64 or higher for Xr1000; 1.0.3.68 or higher for Xr300; 1.0.0.76 or higher for D6220 and D7000v2; 1.0.0.108 or higher for D6400; 1.0.0.126 or higher for Dgn2200v4; 1.0.0.80 or higher for V6510; 1.0.0.62 or higher for Dc112a
- 1. Identify the NETGEAR router model from the affected list (Xr1000, Xr300, D6220, D6400, D7000v2, Dgn2200v4, V6510, or Dc112a).
- 2. Access the router's web interface by navigating to the device's IP address (commonly 192.168.1.1) via a web browser.
- 3. Log into the router administration panel with administrator credentials.
- 4. Navigate to the Firmware Update or Administration section of the router settings.
- 5. Check the current firmware version under the router status or advanced settings.
- 6. Download the appropriate firmware update from the NETGEAR support website (kb.netgear.com) for the specific router model.
- 7. In the router's web interface, locate the firmware upload/update option.
- 8. Upload the downloaded firmware file and wait for the update process to complete - do not power off the router during the update.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34983 — 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-34983 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