An issue in DrayTek Vigor310 devices through 4.3.2.6 allows an attacker to obtain sensitive information because the httpd server of the Vigo
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.
- Published
- Oct 3, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 18th percentile
- CWE
- CWE-326
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| draytek | vigor2620 firmware | cpe:2.3:o:draytek:vigor2620_firmware |
| draytek | vigor2620 | cpe:2.3:h:draytek:vigor2620 |
| draytek | vigor2915 firmware | cpe:2.3:o:draytek:vigor2915_firmware |
| draytek | vigor2915 | cpe:2.3:h:draytek:vigor2915 |
| draytek | vigor2866 firmware | cpe:2.3:o:draytek:vigor2866_firmware |
| draytek | vigor2866 | cpe:2.3:h:draytek:vigor2866 |
| draytek | vigor2766 firmware | cpe:2.3:o:draytek:vigor2766_firmware |
| draytek | vigor2766 | cpe:2.3:h:draytek:vigor2766 |
| draytek | vigor2865 firmware | cpe:2.3:o:draytek:vigor2865_firmware |
| draytek | vigor2865 | cpe:2.3:h:draytek:vigor2865 |
| draytek | vigor2765 firmware | cpe:2.3:o:draytek:vigor2765_firmware |
| draytek | vigor2765 | cpe:2.3:h:draytek:vigor2765 |
and 36 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- draytek vigor1000b firmware4.4.0.0 and later · before 4.4.3.1
- draytek vigor1000b firmwarebefore 4.3.2.8
- draytek vigor165 firmwarebefore 4.2.7
- draytek vigor166 firmwarebefore 4.2.7
- draytek vigor2133 firmwareall versions
- draytek vigor2135 firmwarebefore 4.4.5.3
- draytek vigor2620 firmwareall versions
- draytek vigor2762 firmwareall versions
- draytek vigor2763 firmwarebefore 4.4.5.3
- draytek vigor2765 firmwarebefore 4.4.5.3
- draytek vigor2766 firmwarebefore 4.4.5.3
- draytek vigor2832 firmwareall versions
- draytek vigor2860 firmwareall versions
- draytek vigor2862 firmwareall versions
- draytek vigor2865 firmwarebefore 4.4.5.2
- draytek vigor2866 firmwarebefore 4.4.5.2
- draytek vigor2915 firmwarebefore 4.4.5.3
- draytek vigor2925 firmwareall versions
- draytek vigor2926 firmwareall versions
- draytek vigor2952 firmwareall versions
Same product
draytek: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-51139Buffer Overflow vulnerability in Vigor2620/LTE200 3.9.8.9 and earlier and Vigor2860/2925 3.9.8 and earlier and Vigor2862/2926 3.9.9.5 and ea39Monitor
- CVE-2023-31447user_login.cgi on Draytek Vigor2620 devices before 3.9.8.4 (and on all versions of Vigor2925 devices) allows attackers to send a crafted pay39Monitor
- CVE-2024-41596Buffer Overflow vulnerabilities exist in DrayTek Vigor310 devices through 4.3.2.6 (in the Vigor management UI) because of improper retrieval32Monitor
- CVE-2024-41588The CGI endpoints v2x00.cgi and cgiwcg.cgi of DrayTek Vigor3910 devices through 4.3.2.6 are vulnerable to buffer overflows, by authenticated32Monitor
- CVE-2024-41591DrayTek Vigor3910 devices through 4.3.2.6 allow unauthenticated DOM-based reflected XSS.24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1601 · Oct 4, 2024(DrayTek Çoklu Ürün Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-326 · Inadequate Encryption StrengthCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- www.forescout.com/resources/draybreak-draytek-research/
- www.forescout.com/resources/draytek14-vulnerabilities
Vendor advisories and official records. Exploit/PoC links are deliberately left out.