# CVE-2023-45887: Code injection in n/a

> Remote attackers can execute arbitrary code on game clients via modified GPCM messages in DS Wireless Communication.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-q8qj-jcw4-vf7x

## What is CVE-2023-45887?

CVE-2023-45887 is a critical code injection vulnerability in n/a, published on 19 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DS Wireless Communication (DWC) with DWC_VERSION_3 and DWC_VERSION_11 allows remote attackers to execute arbitrary code on a game-playing client's machine via a modified GPCM message.

## Which versions are affected by CVE-2023-45887?

It affects 1 product.


Products: Nintendo Ds Wireless Communication.

## How do I fix CVE-2023-45887?

No fix has been published for CVE-2023-45887 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-45887 being exploited?

There is no known exploitation of CVE-2023-45887 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-45887 and fix it if it is affected.

What it is: CVE-2023-45887 is a critical code injection vulnerability in n/a, published on 19 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-45887 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-45887/ (Markdown: https://insights.sbomify.com/CVE-2023-45887/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-45887
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-45887
- OSV: https://osv.dev/vulnerability/CVE-2023-45887

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-45887/
Summaries are generated and may contain mistakes; the official description above is the record.