Mr1100 FirmwareOperating system · Netgear

CVE-2019-20679

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to 12.06.08.00 or later.
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
NETGEAR MR1100 devices before 12.06.08.00 are affected by lack of access control at the function level.

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 MR1100 mobile routers before firmware version 12.06.08.00 contain a broken access control vulnerability where certain functions can be invoked without proper authentication or authorization checks, allowing unauthenticated attackers to potentially execute privileged operations.

MitigationUpdate NETGEAR MR1100 firmware to version 12.06.08.00 or later to remediate the access control deficiency. If patching is not immediately possible, restrict network access to the device management interface.

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
Mr1100 FirmwareOperating system
Affected:< 12.06.08.00

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. Access the router admin interface
    Open a web browser and navigate to the NETGEAR MR1100 management page (typically http://192.168.1.1 or the IP assigned by your ISP). Log in with admin credentials.
    Affected if N/A - this step enables version checking
  2. Locate firmware version information
    In the router admin panel, navigate to the 'Status', 'About', or 'Firmware' section to find the currently installed firmware version number.
    Affected if N/A - this step identifies the version
  3. Compare firmware version against affected range
    Check if the installed firmware version is less than 12.06.08.00. Note the exact version number displayed.
    Affected if The device is affected if the installed firmware version is any version lower than 12.06.08.00
  4. Assess network exposure of management interface
    Determine if the router admin interface is accessible from external/untrusted networks (WAN side) rather than only from trusted local networks (LAN side).
    Affected if The vulnerability is exploitable remotely if the management interface is exposed to untrusted networks

A user is affected if the NETGEAR MR1100 router runs firmware version lower than 12.06.08.00 and has its management interface accessible to untrusted networks.

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 12.06.08.00 or later
Fixed in 12.06.08.00
Interim mitigation

Update NETGEAR MR1100 firmware to version 12.06.08.00 or later to remediate the access control deficiency. If patching is not immediately possible, restrict network access to the device management interface.

Recommended fix High confidence

MR1100 Firmware 12.06.08.00

  1. Navigate to the NETGEAR support page (support.netgear.com) and locate the MR1100 product page
  2. Download firmware version 12.06.08.00 or later from the official downloads section
  3. Access the MR1100 router web interface by entering its IP address in a web browser
  4. Log in with administrator credentials
  5. Navigate to the Advanced tab > Administration > Firmware Update section
  6. Click 'Check for Update' or select 'Upload' to manually load the downloaded firmware file
  7. Wait for the firmware upload to complete and the device to reboot - do not power off during this process
  8. After reboot, verify the firmware version has been updated to 12.06.08.00 or later
Caveat Firmware updates may temporarily disrupt network connectivity; ensure stable power during the upgrade process

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

Fix this in Mr1100 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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