Unauthenticated device crash via pub_key overflow
Published Sep 18, 2024 · Updated Mar 14, 2025
Buffer overflow in v2x00.cgi in DrayTek Vigor 3910 4.3.2.6 allows remote attackers to crash the device via a crafted pub_key value. The handler copies the pub_key value without checking that the destination buffer is large enough, allowing adjacent memory to be overwritten. No authentication or user interaction is required over the network, and the documented consequence is a device crash with no data impact.
Summary
What happened
Buffer overflow in v2x00.cgi in DrayTek Vigor 3910 4.3.2.6 allows remote attackers to crash the device via a crafted pub_key value. The handler copies the pub_key value without checking that the destination buffer is large enough, allowing adjacent memory to be overwritten. No authentication or user interaction is required over the network, and the documented consequence is a device crash with no data impact.
The record
- CVE
- CVE-2024-46560
- Published
- Sep 18, 2024
- Updated
- Mar 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2024CVE publishedPublication date reported by the CVE source.
- Mar 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo