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

> Attackers can trigger a stack buffer overflow in the router's web interface via crafted HTTP requests, potentially leading to remote code execution or denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-fhxp-qvcg-hj2q

## What is CVE-2024-34196?

CVE-2024-34196 is a high-severity memory corruption vulnerability in n/a, published on 8 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Totolink AC1200 Wireless Dual Band Gigabit Router A3002RU_V3 Firmware V3.0.0-B20230809.1615 is vulnerable to Buffer Overflow. The "boa" program allows attackers to modify the value of the "vwlan_idx" field via "formMultiAP". This can lead to a stack overflow through the "formWlEncrypt" CGI function by constructing malicious HTTP requests and passing a WLAN SSID value exceeding the expected length, potentially resulting in command execution or denial of service attacks.

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

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

It affects 1 product.


Products: Totolink A3002ru-V3 Firmware.

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

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

## Is CVE-2024-34196 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-34196 is a high-severity memory corruption vulnerability in n/a, published on 8 May 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-34196 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-34196/ (Markdown: https://insights.sbomify.com/CVE-2024-34196/index.md)
```

## Sources

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

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