CVE-2019-20764
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 R7800 devices before 1.0.2.52 are affected by a stack-based buffer overflow by an authenticated user.
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 confidenceNETGEAR R7800 routers before firmware version 1.0.2.52 contain a stack-based buffer overflow vulnerability in their web management interface. An authenticated attacker can exploit this by sending specially crafted requests to the device, potentially allowing code execution or 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.0.2.52CVSS 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.
-
Confirm device model is NETGEAR R7800Access the router web management interface (typically at 192.168.1.1) and check the device information page, or look for R7800 labeling on the physical deviceAffected if The device is not a NETGEAR R7800 router, as this specific vulnerability only affects that model
-
Check firmware version via web interfaceLog into the router administration page, navigate to Administration > Firmware Update or Router Status page, and locate the firmware version fieldAffected if The displayed firmware version is lower than 1.0.2.52 (for example, 1.0.2.48 or 1.0.2.50)
-
Verify web management interface is enabledAttempt to access the router login page at the default gateway IP address (commonly 192.168.1.1) using a web browserAffected if The web interface is accessible and responds, indicating the management interface is enabled
-
Confirm firmware version is vulnerableCompare your installed firmware version number against the affected range: any version before 1.0.2.52 is vulnerableAffected if The firmware version starts with anything less than 1.0.2.52 (such as 1.0.2.51, 1.0.2.50, 1.0.2.40, or any 1.0.2.x version)
You are affected if you own a NETGEAR R7800 router running firmware version lower than 1.0.2.52 with the web management interface accessible.
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.2.52
Update NETGEAR R7800 firmware to version 1.0.2.52 or later to patch the vulnerability. Restrict administrative access to trusted networks and change default credentials.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20764 — 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-20764 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