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

> Authenticated attackers can trigger buffer overflows in CGI endpoints via POST requests, potentially leading to code execution or privilege escalation on DrayTek Vigor310 devices.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 3 Oct 2024
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-gx28-329m-22gw

## What is CVE-2024-41590?

CVE-2024-41590 is a high-severity memory corruption vulnerability in Draytek Vigor3910 Firmware, published on 3 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Several CGI endpoints are vulnerable to buffer overflows, by authenticated users, because of missing bounds checking on parameters passed through POST requests to the strcpy function on DrayTek Vigor310 devices through 4.3.2.6.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 24 products.


Products: Draytek Vigor1000b Firmware, Draytek Vigor165 Firmware, Draytek Vigor166 Firmware, Draytek Vigor2133 Firmware, Draytek Vigor2135 Firmware, Draytek Vigor2620 Firmware, Draytek Vigor2762 Firmware, Draytek Vigor2763 Firmware, Draytek Vigor2765 Firmware, Draytek Vigor2766 Firmware, Draytek Vigor2832 Firmware, Draytek Vigor2860 Firmware, Draytek Vigor2862 Firmware, Draytek Vigor2865 Firmware, Draytek Vigor2866 Firmware, Draytek Vigor2915 Firmware, Draytek Vigor2925 Firmware, Draytek Vigor2926 Firmware, Draytek Vigor2952 Firmware, Draytek Vigor2962 Firmware and 4 more.

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

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

## Is CVE-2024-41590 being exploited?

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

## Other vulnerabilities in Draytek Vigor3910 Firmware

- [CVE-2022-32548](https://insights.sbomify.com/CVE-2022-32548/): Memory corruption in n/a (critical 10.0)
- [CVE-2024-51138](https://insights.sbomify.com/CVE-2024-51138/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-51139](https://insights.sbomify.com/CVE-2024-51139/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-41593](https://insights.sbomify.com/CVE-2024-41593/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-41588](https://insights.sbomify.com/CVE-2024-41588/): Memory corruption in n/a (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41590 is a high-severity memory corruption vulnerability in Draytek Vigor3910 Firmware, published on 3 Oct 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-41590 in the wild and no public exploit code.

Affected product: Draytek Vigor3910 Firmware. 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-41590/ (Markdown: https://insights.sbomify.com/CVE-2024-41590/index.md)
```

## Sources

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

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