cve.bz

CVE-2024-51138 draytek: Stack-based Buffer Overflow

9.8 criticalEPSS 1.1%

Critical (9.8) in draytek. EPSS 1.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
1.1% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 65th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2025-02-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-121 Stack-based Buffer Overflow
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2024-51138 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-51138?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-51138?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-51138 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
draytek:vigor3912_firmwarebefore 4.4.3.2
draytek:vigor2620_firmwarebefore 3.9.9.1
draytek:vigorlte200_firmwarebefore 3.9.9.1
draytek:vigor2860_firmwarebefore 3.9.8.3
draytek:vigor2925_firmwarebefore 3.9.8.3
draytek:vigor2862_firmwarebefore 3.9.9.8
draytek:vigor2926_firmwarebefore 3.9.9.8
draytek:vigor2133_firmwarebefore 3.9.9.2
draytek:vigor2762_firmwarebefore 3.9.9.2
draytek:vigor2832_firmwarebefore 3.9.9.2
draytek:vigor2135_firmwarebefore 4.4.5.5
draytek:vigor2765_firmwarebefore 4.4.5.5
draytek:vigor2766_firmwarebefore 4.4.5.5
draytek:vigor2763_firmwarebefore 4.4.5.5
draytek:vigor2865_firmwarebefore 4.4.5.8
draytek:vigor2866_firmwarebefore 4.4.5.8
draytek:vigor2927_firmwarebefore 4.4.5.8
draytek:vigor2962_firmwarebefore 4.3.2.9
draytek:vigor2962_firmwarefrom 4.4.3 before 4.4.3.2
draytek:vigor3910_firmwarebefore 4.3.2.9
draytek:vigor3910_firmwarefrom 4.4.3 before 4.4.3.2
draytek:vigor2915_firmwarebefore 4.4.5
draytek:vigor1000b_firmwarebefore 4.4.3.2
draytek:vigor2952_firmwarebefore 3.9.8.5
draytek:vigor3220_firmwarebefore 3.9.8.5

References

Check your stackJSON