CVE-2021-38516
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 · uneditedCertain NETGEAR devices are affected by lack of access control at the function level. This affects D6220 before 1.0.0.48, D6400 before 1.0.0.82, D7000v2 before 1.0.0.52, D7800 before 1.0.1.44, D8500 before 1.0.3.43, DC112A before 1.0.0.40, DGN2200v4 before 1.0.0.108, RBK50 before 2.3.0.32, RBR50 before 2.3.0.32, RBS50 before 2.3.0.32, RBK20 before 2.3.0.28, RBR20 before 2.3.0.28, RBS20 before 2.3.0.28, RBK40 before 2.3.0.28, RBR40 before 2.3.0.28, RBS40 before 2.3.0.28, R6020 before 1.0.0.34, R6080 before 1.0.0.34, R6120 before 1.0.0.44, R6220 before 1.1.0.80, R6230 before 1.1.0.80, R6250 before 1.0.4.34, R6260 before 1.1.0.40, R6850 before 1.1.0.40, R6350 before 1.1.0.40, R6400v2 before 1.0.2.62, R6700v3 before 1.0.2.62, R6700v2 before 1.2.0.36, R6800 before 1.2.0.36, R6900v2 before 1.2.0.36, R7000 before 1.0.9.34, R6900P before 1.3.1.44, R7000P before 1.3.1.44, R7100LG before 1.0.0.48, R7200 before 1.2.0.48, R7350 before 1.2.0.48, R7400 before 1.2.0.48, R7450 before 1.2.0.36, AC2100 before 1.2.0.36, AC2400 before 1.2.0.36, AC2600 before 1.2.0.36, R7500v2 before 1.0.3.38, R7800 before 1.0.2.58, R7900 before 1.0.3.8, R7960P before 1.4.1.44, R8000 before 1.0.4.28, R7900P before 1.4.1.30, R8000P before 1.4.1.30, R8900 before 1.0.4.2, R9000 before 1.0.4.2, RAX120 before 1.0.0.74, RBK752 before 3.2.16.6, RBR750 before 3.2.16.6, RBS750 before 3.2.16.6, RBK852 before 3.2.16.6, RBR850 before 3.2.16.6, RBS850 before 3.2.16.6, WNR3500Lv2 before 1.2.0.56, XR450 before 2.3.2.32, and XR500 before 2.3.2.32.
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 confidenceThis is a broken access control vulnerability in multiple NETGEAR router firmware versions where certain privileged functions lack proper authentication or authorization checks. An unauthenticated attacker can directly access sensitive administrative functions without valid credentials, potentially leading to full device compromise.
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.48< 1.0.0.82< 1.0.0.52< 1.0.1.44< 1.0.3.43< 1.0.0.40< 1.0.0.108< 2.3.0.32CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the NETGEAR router modelLocate the device model number on the router label or check the admin interface System or Maintenance section for the exact model designationAffected if The device model is D6220, D6400, D7000, D7800, D8500, DC112A, DGN2200, or RBK50
-
Check the installed firmware versionAccess the router admin web interface, navigate to Administration > Firmware Update or a similar System/Management section, and note the current firmware version displayedAffected if The displayed firmware version is below the threshold for your model (D6220: 1.0.0.48, D6400: 1.0.0.82, D7000: 1.0.0.52, D7800: 1.0.1.44, D8500: 1.0.3.43, DC112A: 1.0.0.40, DGN2200: 1.0.0.108, RBK50: 2.3.0.32)
-
Confirm network accessibility of management interfaceAttempt to access the router admin web interface from an untrusted network segment or verify that remote administration is enabled in the router settings under Administration > Remote ManagementAffected if The admin interface is reachable from an untrusted network or remote administration is enabled and the firmware version is below the patched threshold
You are affected if your NETGEAR router model matches one of the eight affected models AND the installed firmware version is lower than the specified threshold for that model.
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.401.0.0.481.0.0.52
Update affected NETGEAR devices to the patched firmware versions specified in the vendor advisory. If updates are unavailable, restrict network access to management interfaces and disable remote administration.
Device-specific minimum fixed firmware versions (e.g., D6220: 1.0.0.48, D6400: 1.0.0.82, D7000: 1.0.0.52, D7800: 1.0.1.44, D8500: 1.0.3.43, DC112A: 1.0.0.40, DGN2200: 1.0.0.108, RBK50: 2.3.0.32)
- Identify your specific NETGEAR device model from the affected list
- Navigate to the NETGEAR support website (kb.netgear.com) or use the NETGEAR Nighthawk/Orbi app
- Locate the firmware download section for your device model
- Download the firmware version equal to or newer than the fixed version specified in the advisory (e.g., D6220: 1.0.0.48, D6400: 1.0.0.82, D7000: 1.0.0.52, D7800: 1.0.1.44, D8500: 1.0.3.43, DC112A: 1.0.0.40, DGN2200: 1.0.0.108, RBK50: 2.3.0.32)
- Access your router's web management interface via browser (typically http://routerlogin.net or http://192.168.1.1)
- Navigate to Advanced > Administration > Firmware Update or similar path
- Upload and apply the downloaded firmware file
- Wait for the router to complete the firmware update and reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-38516 — 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-38516 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