CVE-2019-20745
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 command injection by an authenticated user. This affects WAC505 before 5.0.10.2 and WAC510 before 5.0.10.2.
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 confidenceAuthenticated users can inject and execute arbitrary operating system commands on NETGEAR WAC505 and WAC510 wireless access point devices due to insufficient input validation in the firmware. The vulnerability is exploitable through the web management interface or CLI after successful authentication.
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< 5.0.10.2< 5.0.10.2CVSS 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 device model and firmware versionAccess the web management interface (http://[device IP]) and navigate to Administration > Firmware Upgrade, or use CLI command 'show version' to retrieve the current firmware version.Affected if The device is a NETGEAR WAC505 or WAC510 running firmware version lower than 5.0.10.2.
-
Confirm web management interface accessibilityVerify if the device web interface (TCP port 80/443) is reachable from network segments that contain untrusted users.Affected if The web management interface is exposed to untrusted networks and the firmware version is below 5.0.10.2.
-
Verify CLI accessibilityCheck if telnet or SSH access to the device is enabled and accessible from external or untrusted network segments.Affected if CLI access is enabled and exposed to untrusted networks while running vulnerable firmware.
-
Review administrative accountsAudit the list of configured administrator accounts in the web interface under Administration > User Account to identify any unauthorized or unexpected accounts.Affected if Unexpected administrative accounts exist on a device running vulnerable firmware, indicating potential compromise.
The device is affected if it is a NETGEAR WAC505 or WAC510 running firmware version earlier than 5.0.10.2 and the management interfaces are accessible to the attacker.
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 data5.0.10.2
Upgrade NETGEAR WAC505 and WAC510 firmware to version 5.0.10.2 or later. If immediate patching is not feasible, limit administrative access to trusted IP addresses only and monitor for suspicious administrative activity.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20745 — 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-20745 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