CVE-2020-28373
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 · uneditedupnpd on certain NETGEAR devices allows remote (LAN) attackers to execute arbitrary code via a stack-based buffer overflow. This affects R6400v2 V1.0.4.102_10.0.75, R6400 V1.0.1.62_1.0.41, R7000P V1.3.2.126_10.1.66, XR300 V1.0.3.50_10.3.36, R8000 V1.0.4.62, R8300 V1.0.2.136, R8500 V1.0.2.136, R7300DST V1.0.0.74, R7850 V1.0.5.64, R7900 V1.0.4.30, RAX20 V1.0.2.64, RAX80 V1.0.3.102, and R6250 V1.0.4.44.
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 confidenceA stack-based buffer overflow vulnerability exists in the upnpd (UPnP daemon) service on multiple NETGEAR router models. Remote attackers on the local network can exploit this pre-authentication vulnerability to execute arbitrary code by overflowing a stack buffer in the UPnP service, achieving full compromise of the affected 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= 1.0.4.102_10.0.75= 1.0.1.62_1.0.41= 1.3.2.126_10.1.66= 1.0.3.50_10.3.36= 1.0.4.62= 1.0.2.136= 1.0.2.136= 1.0.0.74CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:A/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 modelCheck the device label on the router or log into the web administration interface to confirm the exact model number (R6400v2, R6400, R7000p, Xr300, R8000, R8300, R8500, or R7300dst)Affected if The model is one of: R6400v2, R6400, R7000p, Xr300, R8000, R8300, R8500, or R7300dst
-
Check the installed firmware versionLog into the NETGEAR web interface (typically at 192.168.1.1) and navigate to Administration > Firmware Update or Router Info to view the current firmware versionAffected if The firmware version matches: 1.0.4.102_10.0.75 (R6400v2), 1.0.1.62_1.0.41 (R6400), 1.3.2.126_10.1.66 (R7000p), 1.0.3.50_10.3.36 (Xr300), 1.0.4.62 (R8000), 1.0.2.136 (R8300), 1.0.2.136 (R8500), or 1.0.0.74 (R7300dst)
-
Verify if UPnP service is enabledLog into the NETGEAR web interface and navigate to Advanced > Advanced Setup > UPnP to check if UPnP is turned onAffected if UPnP is enabled on the device
The device is affected if it is one of the listed models, runs one of the specified firmware versions, and has UPnP enabled, as the vulnerability exists in the upnpd service and can be exploited by remote attackers on the local network 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.
From vendor dataApply available NETGEAR firmware updates for affected models; if patches are unavailable (end-of-life devices), replace the routers and consider disabling UPnP as a temporary compensating control while planning replacement.
- Consultation4.0 h
- Implementation2.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28373 — 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-2020-28373 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