dbcve.org
M4200 10mg Poe\+ FirmwareOperating system · Netgear

CVE-2017-18858

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-28
Fix available
A fix is available. Upgrade to after 12.0.2.11 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
Certain NETGEAR devices are affected by command execution. This affects M4200-10MG-POE+ 12.0.2.11 and earlier, M4300-28G 12.0.2.11 and earlier, M4300-52G 12.0.2.11 and earlier, M4300-28G-POE+ 12.0.2.11 and earlier, M4300-52G-POE+ 12.0.2.11 and earlier, M4300-8X8F 12.0.2.11 and earlier, M4300-12X12F 12.0.2.11 and earlier, M4300-24X24F 12.0.2.11 and earlier, M4300-24X 12.0.2.11 and earlier, and M4300-48X 12.0.2.11 and earlier.

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

Unauthenticated command execution vulnerability in NETGEAR M4200 and M4300 series switches running firmware 12.0.2.11 and earlier. The CVSS 9.8 score indicates the vulnerability is network-accessible without authentication, likely through command injection in a web service or API endpoint.

MitigationUpdate affected devices to firmware newer than 12.0.2.11. If immediate patching is not feasible, restrict management interface access to trusted networks or disable the vulnerable service.

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
M4200 10mg Poe\+ FirmwareOperating system
Affected:<= 12.0.2.11
M4300 28g FirmwareOperating system
Affected:<= 12.0.2.11
M4300 52g FirmwareOperating system
Affected:<= 12.0.2.11
M4300 28g Poe\+ FirmwareOperating system
Affected:<= 12.0.2.11
M4300 52g Poe\+ FirmwareOperating system
Affected:<= 12.0.2.11
M4300 8x8f FirmwareOperating system
Affected:<= 12.0.2.11
M4300 12x12f FirmwareOperating system
Affected:<= 12.0.2.11
M4300 24x24f FirmwareOperating system
Affected:<= 12.0.2.11

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 the switch model
    Access the device web interface or check the physical device label to confirm the exact model number (M4200 or one of the M4300 variants: 28g, 52g, 28g Poe+, 52g Poe+, 8x8f, 12x12f, 24x24f)
    Affected if The model is not one of the listed affected models (M4200 or M4300 series variants)
  2. Check the firmware version
    Log into the switch web interface and navigate to Maintenance > Firmware Upgrade, or use the CLI command 'show version' to retrieve the current firmware build number
    Affected if The firmware version is 12.0.2.11 or earlier (any version <= 12.0.2.11)
  3. Verify management interface accessibility
    Attempt to reach the device web interface over HTTP/HTTPS from a remote system, or check network ACLs/firewall rules that permit access to the management IP on ports 80/443
    Affected if The management web interface is reachable from an untrusted network (not limited to admin/VLAN-only access)
  4. Confirm the device is not segmented
    Review network segmentation: verify the management interface is on a dedicated management VLAN or behind a jump host, not directly exposed to the general network
    Affected if The switch management IP is directly accessible from user/dataplane networks without authentication barriers

You are affected if the device is an M4200 or M4300 series model running firmware version 12.0.2.11 or earlier and the management interface is accessible from your network.

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 a release after 12.0.2.11
Interim mitigation

Update affected devices to firmware newer than 12.0.2.11. If immediate patching is not feasible, restrict management interface access to trusted networks or disable the vulnerable service.

Recommended fix Moderate confidence

Any firmware version newer than 12.0.2.11 that includes the security patch for command injection

  1. 1. Identify the exact model number of the NETGEAR switch from the M4200 or M4300 series
  2. 2. Navigate to the NETGEAR support website (support.netgear.com) or the knowledge base at kb.netgear.com
  3. 3. Locate the firmware download section for your specific model
  4. 4. Download the latest available firmware version (version higher than 12.0.2.11)
  5. 5. Review the firmware release notes to confirm security fixes are included
  6. 6. Backup the current device configuration
  7. 7. Access the device web management interface or console
  8. 8. Upload and install the new firmware version
Caveat Review release notes for any configuration or feature changes between versions; some legacy features may be deprecated in newer firmware

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

Fix this in M4200 10mg Poe\+ Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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