# CVE-2024-34454: Security feature bypass in n/a

> Man-in-the-middle attackers can forge SSL certificates on Nintendo Wii U OS by exploiting a flawed secondary verification mechanism that ignores CA details and signatures.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2024-34454?

CVE-2024-34454 is a high-severity vulnerability in n/a, published on 26 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nintendo Wii U OS 5.5.5 allows man-in-the-middle attackers to forge SSL certificates as though they came from a Root CA, because there is a secondary verification mechanism that only checks whether a CA is known and ignores the CA details and signature (and because * is accepted as a Common Name).

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-34454?


## How do I fix CVE-2024-34454?

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

## Is CVE-2024-34454 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34454 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34454 and fix it if it is affected.

What it is: CVE-2024-34454 is a high-severity vulnerability in n/a, published on 26 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34454 exists.

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-2024-34454/ (Markdown: https://insights.sbomify.com/CVE-2024-34454/index.md)
```

## Sources

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

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