# CVE-2024-29075: Information disclosure in Mesh Wi-Fi router RP562B

> An authenticated network-adjacent attacker can read or modify device settings due to active debug code in the router firmware.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2024
- **Updated:** 12 Nov 2024
- **Also known as:** GHSA-vfj7-wc6m-2f4v

## What is CVE-2024-29075?

CVE-2024-29075 is a medium-severity vulnerability in SoftBank Corp. Mesh Wi-Fi router RP562B, published on 12 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Active debug code vulnerability exists in Mesh Wi-Fi router RP562B firmware version v1.0.2 and earlier. If this vulnerability is exploited, a network-adjacent authenticated attacker may obtain or alter the settings of the device .

Weakness: CWE-489 (Active Debug Code)

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


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

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

## Is CVE-2024-29075 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29075 is a medium-severity vulnerability in SoftBank Corp. Mesh Wi-Fi router RP562B, published on 12 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-29075 in the wild and no public exploit code.

Affected product: SoftBank Corp. Mesh Wi-Fi router RP562B. 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-29075/ (Markdown: https://insights.sbomify.com/CVE-2024-29075/index.md)
```

## Sources

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

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