Unauthenticated service interruption via sProfName buffer overflow
Published Sep 18, 2024 · Updated Mar 18, 2025
Buffer overflow in DrayTek Vigor3910 firmware 4.3.2.6 allows remote attackers to interrupt service through crafted sProfName input. The v2x00.cgi endpoint accepts an oversized attacker-controlled sProfName parameter and overflows an internal buffer; public records do not identify the affected copy operation. Network access requires no authentication or user interaction, while public evidence does not distinguish whether the resulting interruption is a hang, crash, or reboot.
Summary
What happened
Buffer overflow in DrayTek Vigor3910 firmware 4.3.2.6 allows remote attackers to interrupt service through crafted sProfName input. The v2x00.cgi endpoint accepts an oversized attacker-controlled sProfName parameter and overflows an internal buffer; public records do not identify the affected copy operation. Network access requires no authentication or user interaction, while public evidence does not distinguish whether the resulting interruption is a hang, crash, or reboot.
The record
- CVE
- CVE-2024-46581
- Published
- Sep 18, 2024
- Updated
- Mar 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2024CVE publishedPublication date reported by the CVE source.
- Mar 18, 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