Wac104 FirmwareOperating system · Netgear

CVE-2021-38532

HIGH · 7.2 CVSS v3.1 Published 2021-08-11
Fix available
A fix is available. Upgrade to 1.0.4.15 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
NETGEAR WAC104 devices before 1.0.4.15 are affected by incorrect configuration of security settings.

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 confidence

NETGEAR WAC104 wireless access point devices running firmware versions prior to 1.0.4.15 contain incorrect configuration of security settings, likely involving exposed management interfaces, weak security defaults, or improper access controls that could allow authenticated attackers to modify device configuration.

MitigationUpgrade NETGEAR WAC104 firmware to version 1.0.4.15 or later to remediate the security misconfiguration.

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
Wac104 FirmwareOperating system
Affected:< 1.0.4.15

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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

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

  1. Identify the device model
    Access the device web management interface (typically at 192.168.1.1) and check the device information page, or physically inspect the device label for the model number WAC104
    Affected if The device is not a NETGEAR WAC104 model, then this specific CVE does not apply
  2. Check the firmware version
    In the device web interface, navigate to the Administration or Status section to view the firmware version. Compare this version number against 1.0.4.15
    Affected if The installed firmware version is lower than 1.0.4.15 (for example, 1.0.4.10 or any version in the 1.0.x range below 1.0.4.15)
  3. Verify management interface exposure
    Check the device network configuration to determine if the web management interface is accessible from the WAN or guest network rather than only from the local LAN. Inspect port forwarding rules or access control settings that may expose port 80/443 externally
    Affected if The management interface (HTTP/HTTPS on ports 80/443) is configured to be accessible from outside the trusted local network, or port forwarding exposes it to untrusted networks

You are affected if your NETGEAR WAC104 is running firmware version lower than 1.0.4.15 AND the device management interface is exposed to untrusted networks or has weak access controls.

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.4.15 or later
Fixed in 1.0.4.15
Interim mitigation

Upgrade NETGEAR WAC104 firmware to version 1.0.4.15 or later to remediate the security misconfiguration.

Recommended fix Moderate confidence

NETGEAR WAC104 Firmware version 1.0.4.15 or later

  1. 1. Download the firmware version 1.0.4.15 or later from the official NETGEAR support website (kb.netgear.com)
  2. 2. Access the NETGEAR WAC104 web management interface by entering the device's IP address in a web browser
  3. 3. Log in with administrator credentials
  4. 4. Navigate to the Administration or Maintenance section
  5. 5. Look for a Firmware Update or Router Update option
  6. 6. Click Browse or Choose File and select the downloaded firmware file
  7. 7. Click Upload or Update to begin the firmware upgrade process
  8. 8. Wait for the upload to complete and for the device to reboot (do not power off the device during this process)
Caveat Firmware upgrades on NETGEAR devices typically retain settings, but it is recommended to backup configuration before upgrading; some legacy features may be deprecated in newer firmware versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wac104 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Check whether your project pulls in CVE-2021-38532 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-38532 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