# CVE-2024-40750: Information disclosure in n/a

> Attackers can intercept cleartext Wi-Fi passwords transmitted during app-based installation of Linksys Velop devices.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 9 Jul 2024
- **Updated:** 22 Nov 2024
- **Also known as:** GHSA-2jrh-c5mc-7j55

## What is CVE-2024-40750?

CVE-2024-40750 is a medium-severity vulnerability in n/a, published on 9 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Linksys Velop Pro 6E 1.0.8 MX6200_1.0.8.215731 and 7 1.0.10.215314 devices send cleartext Wi-Fi passwords over the public Internet during app-based installation.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 2 products.


Products: Linksys Mbe7000 Firmware, Linksys Mx6200 Firmware.

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

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

## Is CVE-2024-40750 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-40750 is a medium-severity vulnerability in n/a, published on 9 Jul 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-40750 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-2024-40750/ (Markdown: https://insights.sbomify.com/CVE-2024-40750/index.md)
```

## Sources

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

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