Wab S600 Ps FirmwareOperating system · Elecom

CVE-2023-40072

HIGH · 8.8 CVSS v3.1 Published 2023-08-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
OS command injection vulnerability in ELECOM wireless LAN access point devices allows an authenticated user to execute an arbitrary OS command by sending a specially crafted request.

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 confidence

OS command injection vulnerability in ELECOM wireless LAN access points allows an authenticated attacker to execute arbitrary OS commands by sending specially crafted requests. The vulnerability stems from improper input validation when processing user requests, allowing command separators or shell metacharacters to be passed to underlying system calls.

MitigationApply available firmware updates from ELECOM. If no patch is available, restrict administrative access to trusted networks only and consider network segmentation to limit exposure.

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
Wab S600 Ps FirmwareOperating system
Affected:all versions
Wab S300 FirmwareOperating system
Affected:all versions

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 device model
    Access the device web interface or check the device label for the exact model number. Look for 'Wab S600 Ps' or 'Wab S300' designations.
    Affected if The device model is Elecom Wab S600 Ps or Elecom Wab S300.
  2. Verify admin interface exposure
    Check network configuration to determine if the device administrative interface (HTTP/HTTPS on ports 80/443 or vendor-specific ports) is reachable from untrusted networks. Use external port scanning tools or review firewall rules.
    Affected if The administrative web interface is accessible from networks outside the trusted administrative zone.
  3. Review authentication settings
    Log into the device admin panel and examine user accounts, authentication methods, and any default credentials still in use. Check if weak or default passwords are configured.
    Affected if Default credentials remain unchanged or weak authentication is configured.
  4. Check for unauthorized access indicators
    Review system logs, connection logs, and any available audit trails for suspicious commands, unexpected IP addresses accessing the admin interface, or unusual request patterns containing shell metacharacters.
    Affected if Logs show unexpected administrative logins, requests containing characters like ; | & $ ` or unusual command patterns.
  5. Review network segmentation
    Verify whether the device management VLAN or network segment is properly isolated from general user traffic. Check router/firewall configurations that control access to the device.
    Affected if The device admin interface is on the same network segment as general user devices without proper access controls.

You are affected if you are running an Elecom Wab S600 Ps or Wab S300 access point with its administrative interface exposed to untrusted networks, regardless of firmware version since all versions are vulnerable.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available firmware updates from ELECOM. If no patch is available, restrict administrative access to trusted networks only and consider network segmentation to limit exposure.

Fix this in Wab S600 Ps Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-40072 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