CVE-2018-21122
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 · uneditedCertain NETGEAR devices are affected by denial of service. This affects GS110EMX before 1.0.0.9, GS810EMX before 1.0.0.5, XS512EM before 1.0.0.6, and XS724EM before 1.0.0.6.
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 confidenceDenial of service vulnerability affecting NETGEAR GS110EMX, GS810EMX, XS512EM, and XS724EM switches. The specific technical details of the DoS trigger are not provided in the CVE description, but it is network-accessible based on the CVSS score.
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< 1.0.0.9< 1.0.0.5< 1.0.0.6< 1.0.0.6CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the switch modelCheck the device label, web management interface, or CLI output to confirm the exact model number (GS110EMX, GS810EMX, XS512EM, or XS724EM)Affected if The model is one of GS110EMX, GS810EMX, XS512EM, or XS724EM
-
Determine the installed firmware versionAccess the switch web interface, CLI (via telnet/ssh), or SNMP to retrieve the current firmware versionAffected if The firmware version cannot be determined or is below the fixed version for your model
-
Compare firmware version against affected rangesCompare the installed version to the vulnerable ranges: GS110EMX < 1.0.0.9, GS810EMX < 1.0.0.5, XS512EM < 1.0.0.6, XS724EM < 1.0.0.6Affected if Firmware version is below the fixed version for your specific model and the switch is network-accessible
You are affected if you own one of the four models and your firmware version is below the corresponding threshold (1.0.0.9 for GS110EMX, 1.0.0.5 for GS810EMX, 1.0.0.6 for XS512EM/XS724EM) and the device management interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data1.0.0.51.0.0.61.0.0.9
Apply the available firmware updates: GS110EMX to version 1.0.0.9 or later, GS810EMX to version 1.0.0.5 or later, and XS512EM/XS724EM to version 1.0.0.6 or later.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-21122 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-21122 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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