dbcve.org
Nbg 418n V2 FirmwareOperating system · Zyxel

CVE-2019-17354

CRITICAL · 9.4 CVSS v3.1 Published 2019-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
wan.htm page on Zyxel NBG-418N v2 with firmware version V1.00(AARP.9)C0 can be accessed directly without authentication, which can lead to disclosure of information about the WAN, and can also be leveraged by an attacker to modify data fields of the page.

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

The Zyxel NBG-418N v2 router with firmware V1.00(AARP.9)C0 contains an authentication bypass vulnerability where the wan.htm page can be accessed directly without any authentication. This allows unauthenticated attackers to view sensitive WAN configuration information and also modify the data fields on this page, potentially allowing configuration changes to the WAN interface.

MitigationApply vendor firmware updates if available; if no update exists, consider network segmentation to limit exposure or replace the affected device. Implement firewall rules to restrict unauthorized access to the device's web interface from untrusted networks.

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
Nbg 418n V2 FirmwareOperating system
Affected:= 1.00\(aarp.9\)c0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 router web interface or check the device label to confirm the model is Zyxel NBG-418N v2
    Affected if Device is not the NBG-418N v2 model - not affected
  2. Check the firmware version
    Access the router web interface, typically at System Settings > Firmware Upgrade or Status page, and identify the exact firmware version string
    Affected if Firmware version is NOT exactly V1.00(AARP.9)C0 - not affected (this vulnerability is specific to this exact version)
  3. Test unauthenticated access to wan.htm
    Open a web browser and navigate to http://<router_ip>/wan.htm without logging into the router. A vulnerable device will display the WAN configuration page without requiring authentication.
    Affected if The wan.htm page loads and displays WAN configuration settings without any login prompt - VULNERABLE

A user is affected if they have a Zyxel NBG-418N v2 router running firmware version V1.00(AARP.9)C0 and the wan.htm page is accessible without authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates if available; if no update exists, consider network segmentation to limit exposure or replace the affected device. Implement firewall rules to restrict unauthorized access to the device's web interface from untrusted networks.

Recommended fix Moderate confidence

Latest firmware version available from Zyxel for NBG-418N v2 (contact Zyxel support for specific version number)

  1. 1. Visit the official Zyxel support website at www.zyxel.com and navigate to the NBG-418N v2 product support page
  2. 2. Locate and download the latest firmware version for the NBG-418N v2 router
  3. 3. Access the router's web administration interface (typically at 192.168.1.1)
  4. 4. Navigate to the Administration or System settings section
  5. 5. Select the firmware upgrade option and upload the downloaded firmware file
  6. 6. Wait for the firmware update process to complete (do not power off the device)
  7. 7. After reboot, verify the wan.htm page now requires authentication
Caveat Firmware updates may reset router configuration to defaults; backup current settings before upgrading

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

Fix this in Nbg 418n V2 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing2.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,640.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-17354 — 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-2019-17354 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