dbcve.org
Wlx222 FirmwareOperating system · Yamaha

CVE-2024-22366

MEDIUM · 6.8 CVSS v3.1 Published 2024-01-24
Fix available
A fix is available. Upgrade to 16.00.19 / 18.00.13 or later.
See remediation →
70/100
Remediation priority · Elevated
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
Active debug code exists in Yamaha wireless LAN access point devices. If a logged-in user who knows how to use the debug function accesses the device's management page, this function can be enabled by performing specific operations. As a result, an arbitrary OS command may be executed and/or configuration settings of the device may be altered. Affected products and versions are as follows: WLX222 firmware Rev.24.00.03 and earlier, WLX413 firmware Rev.22.00.05 and earlier, WLX212 firmware Rev.21.00.12 and earlier, WLX313 firmware Rev.18.00.12 and earlier, and WLX202 firmware Rev.16.00.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 · moderate confidence

Active debug code remains in production firmware of multiple Yamaha wireless LAN access point models. An authenticated user with knowledge of specific management page operations can enable this debug function, leading to arbitrary OS command execution and/or unauthorized configuration changes.

MitigationUpdate each affected device model to the latest firmware version beyond the listed vulnerable revisions (WLX222 Rev.24.00.03, WLX413 Rev.22.00.05, WLX212 Rev.21.00.12, WLX313 Rev.18.00.12, WLX202 Rev.16.00.18).

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
Wlx222 FirmwareOperating system
Affected:< 24.00.04
Wlx413 FirmwareOperating system
Affected:< 22.00.06
Wlx212 FirmwareOperating system
Affected:< 21.00.13
Wlx313 FirmwareOperating system
Affected:< 18.00.13
Wlx202 FirmwareOperating system
Affected:< 16.00.19

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

CVSS:3.1/AV:A/AC:L/PR:H/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 Yamaha access point model
    Log into the device management interface or check the device label to confirm the exact model number (Wlx202, Wlx212, Wlx222, Wlx313, or Wlx413)
    Affected if The device is one of the five affected models listed in the CVE
  2. Check the installed firmware version
    Access the device web management interface and navigate to the firmware or system status page to view the current firmware revision number
    Affected if The firmware version is below 24.00.04 for Wlx222, 22.00.06 for Wlx413, 21.00.13 for Wlx212, 18.00.13 for Wlx313, or 16.00.19 for Wlx202
  3. Locate the debug function in the management interface
    In the device web management interface, look for debug-related pages, hidden pages, or diagnostic functions that may be accessible via direct URL or hidden menu items
    Affected if A debug function or diagnostic page is present and accessible to authenticated users
  4. Verify debug functionality is enabled
    Check if the debug feature has been activated by examining the device configuration or status indicators related to debugging or diagnostics
    Affected if The debug function has been enabled by any authenticated user on the device

The device is affected if it is a Yamaha Wlx series model running firmware version below the specified threshold and the debug functionality is present or has been enabled by an authenticated user.

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 16.00.19 / 18.00.13 / 21.00.13 or later
Fixed in 16.00.1918.00.1321.00.13
Interim mitigation

Update each affected device model to the latest firmware version beyond the listed vulnerable revisions (WLX222 Rev.24.00.03, WLX413 Rev.22.00.05, WLX212 Rev.21.00.12, WLX313 Rev.18.00.12, WLX202 Rev.16.00.18).

Recommended fix High confidence

WLX222: Rev.24.00.04+ | WLX413: Rev.22.00.06+ | WLX212: Rev.21.00.13+ | WLX313: Rev.18.00.13+ | WLX202: Rev.16.00.19+

  1. 1. Identify the exact model of the Yamaha wireless LAN access point (Wlx222, Wlx413, Wlx212, Wlx313, or Wlx202).
  2. 2. Check the current firmware version via the device's management interface or CLI.
  3. 3. Download the appropriate fixed firmware from the official Yamaha support page (www.rtpro.yamaha.co.jp).
  4. 4. For Wlx222: Upgrade to firmware Rev.24.00.04 or later.
  5. 5. For Wlx413: Upgrade to firmware Rev.22.00.06 or later.
  6. 6. For Wlx212: Upgrade to firmware Rev.21.00.13 or later.
  7. 7. For Wlx313: Upgrade to firmware Rev.18.00.13 or later.
  8. 8. For Wlx202: Upgrade to firmware Rev.16.00.19 or later.
Caveat Review Yamaha release notes for any configuration or feature changes between versions before upgrading

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

Fix this in Wlx222 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

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