CVE-2023-37564
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 · uneditedOS command injection vulnerability in ELECOM wireless LAN routers allows a network-adjacent authenticated attacker to execute an arbitrary OS command with a root privilege by sending a specially crafted request. Affected products and versions are as follows: WRC-1167GHBK-S v1.03 and earlier, WRC-1167GEBK-S v1.03 and earlier, WRC-1167FEBK-S v1.04 and earlier, WRC-1167GHBK3-A v1.24 and earlier, and WRC-1167FEBK-A v1.18 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 · high confidenceOS command injection vulnerability in ELECOM wireless LAN routers allows a network-adjacent authenticated attacker to execute arbitrary OS commands with root privileges by sending specially crafted requests to the router's 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<= 1.03<= 1.03<= 1.04<= 1.24<= 1.18CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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 router modelLocate the model number on the router device label or log into the admin interface and check the Status or System Information pageAffected if The model is not one of the affected Elecom models (Wrc 1167ghbk S, Wrc 1167gebk S, Wrc 1167febk S, Wrc 1167ghbk3 A, Wrc 1167febk A)
-
Check installed firmware versionIn the router admin interface, navigate to Status or System Information to view the firmware version. Compare against affected version thresholds: S models <= 1.03/1.04, A models <= 1.24/1.18Affected if The firmware version falls within or below the affected ranges for your specific model
-
Verify remote management is disabledIn the admin interface, check the Remote Management or Access Control settings. Confirm that remote access to the management interface is disabled or restricted to trusted IPs onlyAffected if Remote management is enabled and accessible from WAN or untrusted networks
-
Confirm management interface requires authenticationAttempt to access the router login page. Verify that authentication is required and that default credentials have been changedAffected if The management interface is accessible without authentication or uses default credentials
You are affected if your Elecom router matches one of the five affected models AND runs firmware at or below the version threshold for that model, with the management interface accessible to an authenticated attacker on the network.
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.
dbcve · scopedApply available firmware updates for the affected router models; until patched, restrict access to the router's administrative interface to trusted devices only and ensure strong authentication credentials.
Latest firmware available from www.elecom.co.jp for each specific model (versions beyond those listed as affected: WRC-1167GHBK-S >1.03, WRC-1167GEBK-S >1.03, WRC-1167FEBK-S >1.04, WRC-1167GHBK3-A >1.24, WRC-1167FEBK-A >1.18)
- 1. Identify the exact model number of the ELECOM router (WRC-1167GHBK-S, WRC-1167GEBK-S, WRC-1167FEBK-S, WRC-1167GHBK3-A, or WRC-1167FEBK-A)
- 2. Access the router's web management interface by entering the router's IP address in a web browser
- 3. Log in with administrator credentials
- 4. Navigate to the firmware update or system settings section (typically under 'Management' or 'System')
- 5. Download the latest firmware version from the official ELECOM support website (www.elecom.co.jp) for the specific router model
- 6. In the router's web interface, locate the firmware upgrade option and upload the downloaded firmware file
- 7. Wait for the firmware upload and installation to complete - do not power off the router during this process
- 8. After reboot, verify the firmware version has been updated by checking the router status page
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37564 — 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-37564 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