CVE-2019-20654
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 incorrect configuration of security settings. This affects WAC505 before 8.0.6.4 and WAC510 before 8.0.6.4.
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 WAC505 and WAC510 wireless access point devices running firmware versions prior to 8.0.6.4 contain incorrect security settings in their configuration, creating a security vulnerability exploitable with a CVSS base score of 7.5 (HIGH). The specific nature of the misconfiguration is not detailed in the CVE description.
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< 8.0.6.4< 8.0.6.4CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 device modelAccess the NETGEAR web management interface or check the device label to confirm the model is WAC505 or WAC510Affected if The device is a NETGEAR WAC505 or WAC510
-
Determine the installed firmware versionLog into the web interface and navigate to the Administration > Firmware Update section, or use the device CLI command 'show version' to retrieve the current firmware versionAffected if The firmware version cannot be verified or is below 8.0.6.4
-
Compare firmware version against the affected rangeCompare the installed firmware version number to 8.0.6.4 - any version prior to 8.0.6.4 (for example 8.0.5.3, 7.x.x.x, 6.x.x.x) is within the vulnerable rangeAffected if The installed firmware version is less than 8.0.6.4 (for example 8.0.6.3, 8.0.5.0, or any 7.x/6.x release)
-
Confirm the device is accessible for managementVerify network connectivity to the WAC505/WAC510 device by pinging its IP address and confirming the web management interface is reachableAffected if The device cannot be accessed to verify its firmware version
The device is affected if it is a NETGEAR WAC505 or WAC510 running firmware version lower than 8.0.6.4.
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 data8.0.6.4
Upgrade NETGEAR WAC505 and WAC510 firmware to version 8.0.6.4 or later to resolve the security misconfiguration. Verify the upgrade in a test environment before deploying to production.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20654 — 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-20654 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