CVE-2024-51138: 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…
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 64.8% of all records.
- 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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 27, 2025
- Updated
- Jul 5, 2026
- EPSS
- 1.0% · 64th percentile
- CWE
- CWE-121
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| draytek | vigor3912 firmware | cpe:2.3:o:draytek:vigor3912_firmware |
| draytek | vigor3912 | cpe:2.3:h:draytek:vigor3912 |
| draytek | vigor2620 firmware | cpe:2.3:o:draytek:vigor2620_firmware |
| draytek | vigor2620 | cpe:2.3:h:draytek:vigor2620 |
| draytek | vigorlte200 firmware | cpe:2.3:o:draytek:vigorlte200_firmware |
| draytek | vigorlte200 | cpe:2.3:h:draytek:vigorlte200 |
| draytek | vigor2860 firmware | cpe:2.3:o:draytek:vigor2860_firmware |
| draytek | vigor2860 | cpe:2.3:h:draytek:vigor2860 |
| draytek | vigor2925 firmware | cpe:2.3:o:draytek:vigor2925_firmware |
| draytek | vigor2925 | cpe:2.3:h:draytek:vigor2925 |
| draytek | vigor2862 firmware | cpe:2.3:o:draytek:vigor2862_firmware |
| draytek | vigor2862 | cpe:2.3:h:draytek:vigor2862 |
and 34 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- draytek vigor1000b firmwarebefore 4.4.3.2
- draytek vigor2133 firmwarebefore 3.9.9.2
- draytek vigor2135 firmwarebefore 4.4.5.5
- draytek vigor2620 firmwarebefore 3.9.9.1
- draytek vigor2762 firmwarebefore 3.9.9.2
- draytek vigor2763 firmwarebefore 4.4.5.5
- draytek vigor2765 firmwarebefore 4.4.5.5
- draytek vigor2766 firmwarebefore 4.4.5.5
+12 more rows
- draytek vigor2832 firmwarebefore 3.9.9.2
- draytek vigor2860 firmwarebefore 3.9.8.3
- draytek vigor2862 firmwarebefore 3.9.9.8
- draytek vigor2865 firmwarebefore 4.4.5.8
- draytek vigor2866 firmwarebefore 4.4.5.8
- draytek vigor2915 firmwarebefore 4.4.5
- draytek vigor2925 firmwarebefore 3.9.8.3
- draytek vigor2926 firmwarebefore 3.9.9.8
- draytek vigor2927 firmwarebefore 4.4.5.8
- draytek vigor2952 firmwarebefore 3.9.8.5
- draytek vigor2962 firmwarebefore 4.3.2.9
- draytek vigor2962 firmware4.4.3 and later · before 4.4.3.2
Same product
draytek: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-41593DrayTek Vigor310 devices through 4.3.2.6 allow a remote attacker to execute arbitrary code via the function ft_payload_dns(), because a…39Monitor
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-121 · Stack-based Buffer OverflowCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.