CVE-2023-37563
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 wireless LAN routers are vulnerable to sensitive information exposure, which allows a network-adjacent unauthorized attacker to obtain sensitive information. 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, WRC-1167FEBK-A v1.18 and earlier, WRC-F1167ACF2 all versions, WRC-600GHBK-A all versions, WRC-733FEBK2-A all versions, WRC-1467GHBK-A all versions, WRC-1467GHBK-S all versions, WRC-1900GHBK-A all versions, and WRC-1900GHBK-S 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 · moderate confidenceELECOM wireless LAN routers contain a sensitive information exposure vulnerability that allows network-adjacent unauthorized attackers to obtain sensitive information. The attack vector requires the attacker to be on the same network segment as the affected device.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 exact Elecom router modelCheck the device label on the router or log into the web administration interface to view the product name. Look for model numbers: Wrc 1167ghbk S, Wrc 1167gebk S, Wrc 1167febk S, Wrc 1167ghbk3 A, or Wrc 1167febk A.Affected if The router model matches one of the five affected models listed.
-
Check the installed firmware versionLog into the router web admin interface (typically 192.168.1.1 or 192.168.0.1) and navigate to System or Administration settings to view the firmware version. Alternatively, check the Elecom support page for your model and compare version numbers.Affected if The installed firmware version is at or below the affected threshold: <= 1.03 for S models (except Wrc 1167febk), <= 1.04 for Wrc 1167febk S, <= 1.24 for Wrc 1167ghbk3 A, or <= 1.18 for Wrc 1167febk A.
-
Verify network accessibility of the router management interfaceFrom a device on the same network segment, attempt to access the router web interface on common management ports (HTTP 80, HTTPS 443). Use nmap or similar tool: nmap -p 80,443 <router-ip> to check if the admin interface is responsive from the local network.Affected if The router management web interface is reachable from network segments other than a dedicated management VLAN.
-
Check if UPnP is enabled on the routerLog into the router web administration interface and look for UPnP settings, typically under Advanced or Network settings. Note whether UPnP is enabled or disabled.Affected if UPnP is enabled and accessible from the local network segment.
You are affected if you have one of the five listed Elecom router models running firmware at or below the specified version threshold and the router or its services are accessible from your local 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 dataApply firmware updates if available from ELECOM; for end-of-life devices without updates, implement network segmentation to isolate router management interfaces and disable UPnP or unnecessary services accessible from the local network.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37563 — 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-37563 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