CVE-2024-41593

DrayTek Vigor310 devices through 4.3.2.6 allow a remote attacker to execute arbitrary code via the function ft_payload_dns(), because a byte sign-extension operation occurs for the length argument of a _memcpy call, leading to a heap-based Buffer Overflow.

Published: 2024-10-03 Last update: 2025-03-13 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-41593 is rated High Risk (72.6/100): CVSS Critical severity, with high exploitation likelihood (EPSS 7.69%, 92th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +1.33% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-41593

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-22 6.36% 7.69% +1.33%
2 2026-02-09 7.36% 6.36% -1.00%
3 2026-01-28 — 7.36% —

Full EPSS history (19 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-41593

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-41593

Affected software / configurations for CVE-2024-41593

Vendor Product Version Raw CPE
draytek vigor3912_firmware < 4.3.6.1 cpe:2.3:o:draytek:vigor3912_firmware:*:*:*:*:*:*:*:*
draytek vigor2962_firmware < 4.3.2.8 cpe:2.3:o:draytek:vigor2962_firmware:*:*:*:*:*:*:*:*
draytek vigor2962_firmware >= 4.4.0.0, < 4.4.3.1 cpe:2.3:o:draytek:vigor2962_firmware:*:*:*:*:*:*:*:*
draytek vigor3910_firmware < 4.3.2.8 cpe:2.3:o:draytek:vigor3910_firmware:*:*:*:*:*:*:*:*
draytek vigor3910_firmware >= 4.4.0.0, < 4.4.3.1 cpe:2.3:o:draytek:vigor3910_firmware:*:*:*:*:*:*:*:*
draytek vigor165_firmware < 4.2.7 cpe:2.3:o:draytek:vigor165_firmware:*:*:*:*:*:*:*:*
draytek vigor1000b_firmware < 4.3.2.8 cpe:2.3:o:draytek:vigor1000b_firmware:*:*:*:*:*:*:*:*
draytek vigor1000b_firmware >= 4.4.0.0, < 4.4.3.1 cpe:2.3:o:draytek:vigor1000b_firmware:*:*:*:*:*:*:*:*
draytek vigor166_firmware < 4.2.7 cpe:2.3:o:draytek:vigor166_firmware:*:*:*:*:*:*:*:*
draytek vigor2135_firmware < 4.4.5.3 cpe:2.3:o:draytek:vigor2135_firmware:*:*:*:*:*:*:*:*
draytek vigor2763_firmware < 4.4.5.3 cpe:2.3:o:draytek:vigor2763_firmware:*:*:*:*:*:*:*:*
draytek vigor2765_firmware < 4.4.5.3 cpe:2.3:o:draytek:vigor2765_firmware:*:*:*:*:*:*:*:*
draytek vigor2865_firmware < 4.4.5.2 cpe:2.3:o:draytek:vigor2865_firmware:*:*:*:*:*:*:*:*
draytek vigor2766_firmware < 4.4.5.3 cpe:2.3:o:draytek:vigor2766_firmware:*:*:*:*:*:*:*:*
draytek vigor2866_firmware < 4.4.5.2 cpe:2.3:o:draytek:vigor2866_firmware:*:*:*:*:*:*:*:*
draytek vigor2915_firmware < 4.4.5.3 cpe:2.3:o:draytek:vigor2915_firmware:*:*:*:*:*:*:*:*
draytek vigor2620_firmware — cpe:2.3:o:draytek:vigor2620_firmware:*:*:*:*:*:*:*:*
draytek vigorlte200_firmware — cpe:2.3:o:draytek:vigorlte200_firmware:*:*:*:*:*:*:*:*
draytek vigor2133_firmware — cpe:2.3:o:draytek:vigor2133_firmware:*:*:*:*:*:*:*:*
draytek vigor2762_firmware — cpe:2.3:o:draytek:vigor2762_firmware:*:*:*:*:*:*:*:*
draytek vigor2832_firmware — cpe:2.3:o:draytek:vigor2832_firmware:*:*:*:*:*:*:*:*
draytek vigor2860_firmware — cpe:2.3:o:draytek:vigor2860_firmware:*:*:*:*:*:*:*:*
draytek vigor2862_firmware — cpe:2.3:o:draytek:vigor2862_firmware:*:*:*:*:*:*:*:*
draytek vigor2925_firmware — cpe:2.3:o:draytek:vigor2925_firmware:*:*:*:*:*:*:*:*
draytek vigor2926_firmware — cpe:2.3:o:draytek:vigor2926_firmware:*:*:*:*:*:*:*:*
draytek vigor2952_firmware — cpe:2.3:o:draytek:vigor2952_firmware:*:*:*:*:*:*:*:*
draytek vigor3220_firmware — cpe:2.3:o:draytek:vigor3220_firmware:*:*:*:*:*:*:*:*

References for CVE-2024-41593

cvelogic Threat Intelligence