dbcve.org
Mbr1515 FirmwareOperating system · Netgear

CVE-2019-17373

CRITICAL · 9.8 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
Certain NETGEAR devices allow unauthenticated access to critical .cgi and .htm pages via a substring ending with .jpg, such as by appending ?x=1.jpg to a URL. This affects MBR1515, MBR1516, DGN2200, DGN2200M, DGND3700, WNR2000v2, WNDR3300, WNDR3400, WNR3500, and WNR834Bv2.

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

NETGEAR router firmware contains an authentication bypass where unauthenticated attackers can access restricted .cgi and .htm administrative pages by appending a .jpg parameter (e.g., ?x=1.jpg) to the URL. This enables full administrative access without credentials.

MitigationApply available firmware updates from NETGEAR; if no update exists, disable remote web management and restrict device access to trusted networks only.

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
Mbr1515 FirmwareOperating system
Affected:all versions
Mbr1516 FirmwareOperating system
Affected:all versions
Dgn2200 FirmwareOperating system
Affected:all versions
Dgn2200m FirmwareOperating system
Affected:all versions
Dgnd3700 FirmwareOperating system
Affected:all versions
Wnr2000v2 FirmwareOperating system
Affected:all versions
Wndr3300 FirmwareOperating system
Affected:all versions
Wndr3400 FirmwareOperating system
Affected:all versions

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 router model
    Log into the router admin interface or check the device label to confirm the exact model number (Mbr1515, Mbr1516, Dgn2200, Dgn2200m, Dgnd3700, Wnr2000v2, Wndr3300, or Wndr3400)
    Affected if The model matches one of the affected models listed in the CVE
  2. Confirm firmware version
    Access the router admin interface and navigate to the Firmware Upgrade or Status page to view the installed firmware version
    Affected if Firmware version cannot be determined or the device is running any version (all versions are affected per the CVE)
  3. Check if remote web management is enabled
    In the router admin interface, go to the Remote Management or Access Control settings and verify whether remote access via HTTP/HTTPS is enabled
    Affected if Remote web management is enabled and the management interface is accessible from untrusted networks
  4. Verify network exposure
    From an external network (not on the local LAN), attempt to access the router login page using the public IP address or domain name
    Affected if The router admin interface is reachable from the internet on port 80 or 443

If the device is one of the affected NETGEAR models and remote web management is accessible from untrusted networks, the environment is vulnerable to this authentication bypass.

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 available firmware updates from NETGEAR; if no update exists, disable remote web management and restrict device access to trusted networks only.

Recommended fix Moderate confidence
  1. 1. Implement network segmentation by placing the affected NETGEAR devices on an isolated VLAN separate from critical systems
  2. 2. If the device supports it, disable remote management/ administration via WAN interface
  3. 3. Restrict access to the device's admin interface by IP address if the firmware provides this option
  4. 4. Consider replacing the affected devices with newer, actively supported models that receive security updates
  5. 5. Monitor NETGEAR's support website periodically for any firmware updates that might address this vulnerability
Caveat Network segmentation may require reconfiguration of existing network topology and access policies

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

Fix this in Mbr1515 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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