CVE-2023-37567
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 · uneditedCommand injection vulnerability in ELECOM and LOGITEC wireless LAN routers allows a remote unauthenticated attacker to execute an arbitrary command by sending a specially crafted request to a certain port of the web management page. Affected products and versions are as follows: WRC-1167GHBK3-A v1.24 and earlier, WRC-F1167ACF2 all versions, WRC-600GHBK-A all versions, WRC-733FEBK2-A all versions, WRC-1467GHBK-A all versions, WRC-1900GHBK-A all versions, and LAN-W301NR all versions.
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 confidenceCommand injection vulnerability in the web management interface of multiple ELECOM and LOGITEC wireless LAN routers allows remote unauthenticated attackers to execute arbitrary operating system commands by sending specially crafted requests to specific ports.
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.24CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelAccess the router's web management interface and check the device information or status page to confirm the exact model number (e.g., Elecom Wrc 1167ghbk3 A or other ELECOM/LOGITEC wireless LAN router models)Affected if The device is an ELECOM or LOGITEC wireless LAN router, particularly the Wrc 1167ghbk3 A model
-
Check firmware versionIn the router's web management interface, navigate to the firmware version or system information section to determine the installed firmware versionAffected if The firmware version is 1.24 or lower on the Elecom Wrc 1167ghbk3 A model, or any unpatched version on other affected ELECOM/LOGITEC models
-
Verify web management interface accessibilityAttempt to access the router's web interface from an external network location by sending an HTTP request to the router's WAN IP address on common management ports (e.g., 80, 443, 8080)Affected if The web management interface is reachable from external networks (WAN-side) without authentication
-
Confirm remote management is enabledIn the router's settings, check the remote management or admin access configuration to see if remote (WAN) access to the web interface is permittedAffected if Remote management or WAN access to the web management interface is enabled in the router configuration
A user is affected if they have an ELECOM or LOGITEC wireless LAN router (such as the Elecom Wrc 1167ghbk3 A) running firmware version 1.24 or lower with the web management interface exposed to remote (WAN) access.
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 dataApply vendor firmware updates when available; if patches are unavailable, restrict network access to the web management interface using firewall rules or by disabling remote management to block external attackers.
- Consultation5.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37567 — 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-2023-37567 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