CVE-2020-5634
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 · uneditedELECOM LAN routers (WRC-2533GST2 firmware versions prior to v1.14, WRC-1900GST2 firmware versions prior to v1.14, WRC-1750GST2 firmware versions prior to v1.14, and WRC-1167GST2 firmware versions prior to v1.10) allow an attacker on the same network segment to execute arbitrary OS commands with a root privilege via unspecified vectors.
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 confidenceELECOM LAN routers (WRC-2533GST2, WRC-1900GST2, WRC-1750GST2, and WRC-1167GST2) running firmware versions prior to v1.14/v1.10 contain a vulnerability allowing an attacker on the same network segment to execute arbitrary OS commands with root privileges via unspecified attack vectors.
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.14< 1.14< 1.14< 1.10CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelLocate the physical router or access its web administration interface and check the model number label (typically on the bottom of the device). Common access paths: http://192.168.0.1 or http://192.168.1.1 for the web UI, or check the device documentation.Affected if The model is one of WRC-2533GST2, WRC-1900GST2, WRC-1750GST2, or WRC-1167GST2.
-
Check the installed firmware versionLog into the router web administration panel, navigate to the System or Administration section, and locate the firmware version information. Alternatively, check the Elecom support website for the specific model and compare the installed version to the affected ranges.Affected if The firmware version is below 1.14 for WRC-2533GST2, WRC-1900GST2, or WRC-1750GST2, or below 1.10 for WRC-1167GST2.
-
Verify network exposureDetermine whether the router management interface is accessible from untrusted network segments. Check if the router has any port forwarding rules, UPnP settings, or remote management features enabled that allow access from the WAN or untrusted LAN devices.Affected if The router management interface is accessible from network segments beyond the trusted local network, or if unknown/untrusted devices can reach the router on the local segment.
-
Review connected devices and network segmentCheck the router DHCP client list or connected devices table to identify all devices on the network segment. Verify which devices have network proximity to the router.Affected if Untrusted or unknown devices exist on the same network segment as the router, providing potential attack access.
A user is affected if they own one of the four specified Elecom router models and the installed firmware version is below the patched release (v1.14 or v1.10 depending on model), combined with the ability for an untrusted attacker to reach the device from the same network segment.
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.101.14
Update router firmware to v1.14 (for WRC-2533GST2, WRC-1900GST2, WRC-1750GST2) or v1.10 (for WRC-1167GST2) or later. If updates are unavailable, restrict network access to trusted devices only.
- Consultation2.0 h
- Implementation3.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5634 — 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-2020-5634 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