CVE-2024-51138
Draytek Vigor2962 Firmware remote code execution
- Published27 Feb 2025
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-51138 being actively exploited?
CVE-2024-51138 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.05%.
How severe is CVE-2024-51138?
CVE-2024-51138 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.05% probability of exploitation.
Which products are affected by CVE-2024-51138?
Affected products include Draytek Vigor1000b Firmware, Draytek Vigor2133 Firmware, Draytek Vigor2135 Firmware, Draytek Vigor2620 Firmware, Draytek Vigor2762 Firmware, and 18 more.
How do I fix CVE-2024-51138?
Upgrade affected software to a fixed version, for example Draytek Vigor1000b Firmware 4.4.3.2, Draytek Vigor2133 Firmware 3.9.9.2, Draytek Vigor2135 Firmware 4.4.5.5 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-51138 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.