# CVE-2024-40083: Memory corruption in n/a

> Remote unauthenticated attackers can execute arbitrary code on Vilo 5 Mesh WiFi Systems via a buffer overflow in the router token function.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Oct 2024
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-rxhf-qxcx-q2rj

## What is CVE-2024-40083?

CVE-2024-40083 is a critical memory corruption vulnerability in n/a, published on 21 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Buffer Overflow vulnerabilty in the local_app_set_router_token function of Vilo 5 Mesh WiFi System <= 5.16.1.33 allows remote, unauthenticated attackers to execute arbitrary code via sscanf reading the token and timezone JSON fields into a fixed-length buffer.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2024-40083 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-40083 is a critical memory corruption vulnerability in n/a, published on 21 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40083 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-40083/ (Markdown: https://insights.sbomify.com/CVE-2024-40083/index.md)
```

## Sources

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

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