Wi Fi Network Adaptor Wap 001 FirmwareOperating system · Nintendo

CVE-2022-36381

HIGH · 7.2 CVSS v3.1 Published 2022-08-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 Nintendo Wi-Fi Network Adaptor WAP-001 All versions allows an attacker with an administrative privilege to execute arbitrary OS commands via unspecified vectors.

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

This is an OS command injection vulnerability in the Nintendo WAP-001 Wi-Fi Network Adaptor affecting all versions. An authenticated attacker with administrative privileges can inject and execute arbitrary operating system commands on the device through unspecified input vectors.

MitigationSince no patches are available for this end-of-life device, remediation requires network isolation, restriction of administrative access, and replacement with a supported network 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
Wi Fi Network Adaptor Wap 001 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 device model
    Physically inspect the device or check network inventory for a Nintendo WAP-001 Wi-Fi Network Adaptor. Check the device label or management interface for model number WAP-001.
    Affected if The device is a Nintendo WAP-001 Wi-Fi Network Adaptor
  2. Confirm administrative access is available
    Check if the device management web interface or CLI is accessible on the network. Verify login credentials for administrative privileges exist or have been configured.
    Affected if The administrative interface is accessible and functional
  3. Inspect for unauthorized processes or connections
    If you have shell access or can capture network traffic, look for unexpected processes, unusual outbound connections, or newly created files that indicate arbitrary command execution.
    Affected if Unexpected processes, unusual network connections, or new files are present that were not intentionally created by administrators

You are affected if you have a Nintendo WAP-001 Wi-Fi Network Adaptor with its administrative interface accessible on your network, as all firmware versions contain the command injection flaw.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since no patches are available for this end-of-life device, remediation requires network isolation, restriction of administrative access, and replacement with a supported network device.

Recommended fix High confidence
  1. 1. Identify all Nintendo Wi-Fi Network Adaptor WAP-001 devices on the network.
  2. 2. Since this is a discontinued product with no available firmware updates, the recommended remediation is to retire and replace the device with a supported alternative.
  3. 3. If the device cannot be immediately replaced, isolate it on a separate network segment with strict access controls to limit the attack surface.
  4. 4. Restrict administrative access to trusted users only, as the vulnerability requires administrative privileges to exploit.
  5. 5. Monitor network traffic for any suspicious command injection attempts.
  6. 6. Consider implementing network intrusion detection systems to alert on potential exploitation attempts.
Caveat Device retirement/replacement required as no firmware updates are available for this discontinued product

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

Fix this in Wi Fi Network Adaptor Wap 001 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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