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

> Remote attackers can execute arbitrary code with elevated privileges via a stack-based buffer overflow in the TR069 STUN server URL parsing.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-mgc5-hg3f-6h7v

## What is CVE-2024-51138?

CVE-2024-51138 is a critical memory corruption vulnerability in Draytek Vigor3910 Firmware, published on 27 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vigor165/166 4.2.7 and earlier; Vigor2620/LTE200 3.9.8.9 and earlier; Vigor2860/2925 3.9.8 and earlier; Vigor2862/2926 3.9.9.5 and earlier; Vigor2133/2762/2832 3.9.9 and earlier; Vigor2135/2765/2766 4.4.5. and earlier; Vigor2865/2866/2927 4.4.5.3 and earlier; Vigor2962 4.3.2.8 and earlier; Vigor3912 4.3.6.1 and earlier; Vigor3910 4.4.3.1 and earlier a stack-based buffer overflow vulnerability has been identified in the URL parsing functionality of the TR069 STUN server. This flaw occurs due to insufficient bounds checking on the amount of URL parameters, allowing an attacker to exploit the overflow by sending a maliciously crafted request. Consequently, a remote attacker can execute arbitrary code with elevated privileges.

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

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

It affects 23 products.


Products: Draytek Vigor1000b 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 Vigor2927 Firmware, Draytek Vigor2952 Firmware, Draytek Vigor2962 Firmware, Draytek Vigor3220 Firmware and 3 more.

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

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

## Is CVE-2024-51138 being exploited?

There is no known exploitation of CVE-2024-51138 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-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)
- [CVE-2024-41590](https://insights.sbomify.com/CVE-2024-41590/): Memory corruption in n/a (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51138 is a critical memory corruption vulnerability in Draytek Vigor3910 Firmware, published on 27 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-51138 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-51138/ (Markdown: https://insights.sbomify.com/CVE-2024-51138/index.md)
```

## Sources

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

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