dbcve.org
Wrc 1167ghbk S FirmwareOperating system · Elecom

CVE-2023-37568

HIGH · 8.0 CVSS v3.1 Published 2023-07-13
Fix available
A fix is available. Upgrade to after 1.03 or later.
See remediation →
82/100
Remediation priority · High
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
ELECOM wireless LAN routers WRC-1167GHBK-S v1.03 and earlier, and WRC-1167GEBK-S v1.03 and earlier allow a network-adjacent authenticated attacker to execute an arbitrary command by sending a specially crafted request to the web management page.

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 confidence

ELECOM WRC-1167GHBK-S and WRC-1167GEBK-S routers versions 1.03 and earlier contain a command injection vulnerability in their web management interface. An authenticated attacker with network adjacency can send specially crafted requests to execute arbitrary OS commands on the device.

MitigationUpdate router firmware to version 1.04 or later. If patching is not immediately possible, disable remote web management, enforce strong authentication, and restrict network access to trusted users.

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
Wrc 1167ghbk S FirmwareOperating system
Affected:<= 1.03
Wrc 1167gebk S FirmwareOperating system
Affected:<= 1.03

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Locate the model number on the device label or web interface status page. Confirm it is either WRC-1167GHBK-S or WRC-1167GEBK-S.
    Affected if The device is one of these two models.
  2. Check the installed firmware version
    Access the router web management interface and navigate to the firmware or system information section. Look for the firmware version number displayed.
    Affected if The firmware version is 1.03 or earlier.
  3. Verify if the web management interface is enabled
    Log into the router admin panel and check the remote management or web interface settings. Confirm whether the web management feature is currently turned on.
    Affected if The web management interface is enabled and accessible.
  4. Assess network accessibility of the web interface
    Determine if the router web interface is reachable from outside the local network. Check for any port forwarding rules or remote management settings that expose the interface.
    Affected if The web interface is accessible from beyond the local network segment.

The device is affected if it is a WRC-1167GHBK-S or WRC-1167GEBK-S router running firmware version 1.03 or earlier with the web management interface enabled and potentially exposed to network adjacency.

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 1.03
Interim mitigation

Update router firmware to version 1.04 or later. If patching is not immediately possible, disable remote web management, enforce strong authentication, and restrict network access to trusted users.

Recommended fix High confidence

Firmware v1.04

  1. Access the web management interface of the ELECOM WRC-1167GHBK-S or WRC-1167GEBK-S router
  2. Navigate to the firmware update section (typically under "Management" or "System" settings)
  3. Download the firmware version 1.04 or later from the official ELECOM support website (www.elecom.co.jp)
  4. Upload the firmware file through the web management interface
  5. Wait for the firmware update process to complete - do not power off the device during this process
  6. After the router restarts, verify the firmware version has been updated to 1.04 or later

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

Fix this in Wrc 1167ghbk S Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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