Code InjectionWeakness · CWE-94

CVE-2024-45200

MEDIUM · 6.3 CVSS v3.1 Published 2024-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
No privileges 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
In Nintendo Mario Kart 8 Deluxe before 3.0.3, the LAN/LDN local multiplayer implementation allows a remote attacker to exploit a stack-based buffer overflow upon deserialization of session information via a malformed browse-reply packet, aka KartLANPwn. The victim is not required to join a game session with an attacker. The victim must open the "Wireless Play" (or "LAN Play") menu from the game's title screen, and an attacker nearby (LDN) or on the same LAN network as the victim can send a crafted reply packet to the victim's console. This enables a remote attacker to obtain complete denial-of-service on the game's process, or potentially, remote code execution on the victim's console. The issue is caused by incorrect use of the Nintendo Pia library,

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

Stack-based buffer overflow in Mario Kart 8 Deluxe's LAN/LDN local multiplayer implementation allows remote attackers to exploit deserialization of malformed browse-reply packets. The vulnerability triggers when a victim opens the Wireless Play/LAN Play menu, enabling remote code execution or denial-of-service via incorrect handling in the Nintendo Pia library.

MitigationUpdate Mario Kart 8 Deluxe to version 3.0.3 or later. Until patched, avoid opening the Wireless Play/LAN Play menu on networks with untrusted devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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. Check Mario Kart 8 Deluxe version
    Open the game and locate the version number displayed on the title screen or in the game options menu under version information.
    Affected if Version is below 3.0.3
  2. Determine if LAN/LDN mode is used
    The vulnerability only triggers when the Wireless Play/LAN Play menu is opened in the game. This menu enables local network discovery for multiplayer sessions.
    Affected if Wireless Play/LAN Play menu is accessed on a network with untrusted devices
  3. Assess local network exposure
    Identify whether the Nintendo Switch is connected to a local network where unknown or untrusted devices may be present. The attack vector is malformed browse-reply packets sent over the LAN.
    Affected if Connected to shared networks where remote attackers can send packets to the Switch

User is affected if Mario Kart 8 Deluxe version is below 3.0.3 and the Wireless Play/LAN Play menu is opened on a network with potentially malicious devices present.

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

Update Mario Kart 8 Deluxe to version 3.0.3 or later. Until patched, avoid opening the Wireless Play/LAN Play menu on networks with untrusted devices.

Recommended fix High confidence

Mario Kart 8 Deluxe version 3.0.3

  1. Ensure your Nintendo Switch console is connected to the internet
  2. From the Nintendo Switch home menu, highlight Mario Kart 8 Deluxe
  3. Press the + button or right-click on the game icon
  4. Select 'Software Update' > 'Update via Internet'
  5. Wait for the game to update to version 3.0.3 or later
  6. After updating, avoid opening the 'Wireless Play' or 'LAN Play' menu when untrusted devices are nearby or on your local network
Caveat No breaking changes expected; this is a standard game update that patches security vulnerabilities

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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