CVE-2019-20748
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 a stack-based buffer overflow by an authenticated user. This affects D7800 before 1.0.1.44, R7500v2 before 1.0.3.38, R7800 before 1.0.2.52, RBK20 before 2.3.0.28, RBR20 before 2.3.0.28, RBS20 before 2.3.0.28, RBK40 before 2.3.0.28, RBS40 before 2.3.0.28, RBK50 before 2.3.0.32, RBR50 before 2.3.0.32, and RBS50 before 2.3.0.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 confidenceA stack-based buffer overflow vulnerability exists in multiple NETGEAR router firmware versions. An authenticated attacker could exploit this to execute arbitrary code or cause a denial of service by overflowing a stack-allocated buffer through the web management interface.
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.1.44< 1.0.3.38< 1.0.2.52< 2.3.0.28< 2.3.0.28< 2.3.0.28< 2.3.0.28< 2.3.0.28CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/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 router modelLocate the model number on the device label or check the web management interface (typically at 192.168.1.1) for the exact model designationAffected if Model is D7800, R7500, R7800, Rbk20, Rbr20, Rbs20, Rbk40, or Rbs40
-
Check installed firmware versionLog into the web management interface and navigate to Administration > Firmware Update or Settings > Router/Network > About to view the current firmware versionAffected if Firmware version is below 1.0.1.44 for D7800, below 1.0.3.38 for R7500, below 1.0.2.52 for R7800, or below 2.3.0.28 for Rbk20/Rbr20/Rbs20/Rbk40/Rbs40
-
Verify web management interface statusCheck if the web management interface is accessible by navigating to the router IP in a browserAffected if Web management interface is accessible (required for exploitation)
-
Check remote administration exposureIn the web management interface, go to Advanced > Remote Management or Administration > Remote Management to see if remote access over WAN is enabledAffected if Remote administration is enabled, allowing exploitation from outside the local network
If the router model and firmware version match the affected ranges AND the web management interface is accessible, the device is vulnerable to CVE-2019-20748
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 data1.0.1.441.0.2.521.0.3.38
Update affected NETGEAR devices to the specified firmware versions (1.0.1.44 for D7800, 1.0.3.38 for R7500v2, 1.0.2.52 for R7800, 2.3.0.28 for RBK20/RBR20/RBS20/RBK40/RBS40, and 2.3.0.32 for RBK50/RBR50/RBS50). If updates are unavailable, restrict web management interface access to trusted networks or disable remote administration.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20748 — 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-2019-20748 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