dbcve.org
Wac505 FirmwareOperating system · Netgear

CVE-2018-21127

HIGH · 8.8 CVSS v3.1 Published 2020-04-22
Fix available
A fix is available. Upgrade to 5.0.0.17 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
Certain NETGEAR devices are affected by command injection by an unauthenticated attacker. This affects WAC505 before 5.0.0.17 and WAC510 before 5.0.0.17.

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 confidence

Unauthenticated command injection vulnerability in NETGEAR WAC505 and WAC510 wireless access points allows remote attackers to execute arbitrary OS commands due to insufficient input validation in firmware versions prior to 5.0.0.17.

MitigationApply vendor firmware version 5.0.0.17 or later to both WAC505 and WAC510 devices to remediate this vulnerability.

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
Wac505 FirmwareOperating system
Affected:< 5.0.0.17
Wac510 FirmwareOperating system
Affected:< 5.0.0.17

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device web management interface or CLI and look for the model number displayed on the status or system information page
    Affected if The device is a Netgear WAC505 or WAC510 model
  2. Check the installed firmware version
    Navigate to the firmware or system information page in the device web interface, or use the CLI command 'show version' or 'get system info' to retrieve the current firmware version
    Affected if The firmware version is lower than 5.0.0.17 (for example, 5.0.0.16, 4.x.x.x, etc.)
  3. Verify network accessibility of the management interface
    Confirm the device management interface (HTTP/HTTPS on port 80/443 or SSH on port 22) is reachable from the network where the attacker would originate their request
    Affected if The device management interface is exposed to an untrusted network without proper access controls

The environment is affected if the device is a WAC505 or WAC510 running firmware version prior to 5.0.0.17 and its management interface is network-accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 5.0.0.17 or later
Fixed in 5.0.0.17
Interim mitigation

Apply vendor firmware version 5.0.0.17 or later to both WAC505 and WAC510 devices to remediate this vulnerability.

Fix this in Wac505 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-21127 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-21127 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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