CVE-2024-41594 json
An issue in DrayTek Vigor310 devices through 4.3.2.6 allows an attacker to obtain sensitive information because the httpd server of the Vig…
published 2024-10-03 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-39091
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
An issue in DrayTek Vigor310 devices through 4.3.2.6 allows an attacker to obtain sensitive information because the httpd server of the Vigor management UI uses a static string for seeding the PRNG of OpenSSL.
Patch / fix
- draytek vigor2915_firmware 4.4.5.3
- draytek vigor2866_firmware 4.4.5.2
- draytek vigor2766_firmware 4.4.5.3
- draytek vigor2865_firmware 4.4.5.2
- draytek vigor2765_firmware 4.4.5.3
- draytek vigor2763_firmware 4.4.5.3
- draytek vigor2135_firmware 4.4.5.3
- draytek vigor166_firmware 4.2.7
- draytek vigor1000b_firmware 4.3.2.8, 4.4.3.1
- draytek vigor165_firmware 4.2.7
- draytek vigor3910_firmware 4.3.2.8, 4.4.3.1
- draytek vigor2962_firmware 4.3.2.8, 4.4.3.1
- draytek vigor3912_firmware 4.3.6.1
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Classification
- Weakness
-
- CWE-326 Inadequate Encryption Strength
References
-
forescout.com
/resources/draytek14-vulnerabilities
broken-link
-
forescout.com
/resources/draybreak-draytek-research/
mitigation, technical-description, third-party-advisory
Sources
- CVE List CVE-2024-41594
- NVD CVE-2024-41594
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.