CVE-2024-46560
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDraytek Vigor 3910 v4.3.2.6 was discovered to contain a buffer overflow in the pub_key parameter at v2x00.cgi. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted input.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA buffer overflow vulnerability exists in the pub_key parameter of the v2x00.cgi web interface on Draytek Vigor 3910 routers running firmware v4.3.2.6. Attackers can send specially crafted input that exceeds the buffer boundaries, causing the device to crash and resulting in a Denial of Service condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.3.2.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelAccess the router's web management interface and look for the device model name, typically displayed on the dashboard or in the System Status or Device Information page. Alternatively, check the login page footer or the administration interface for 'Vigor3910' branding.Affected if The device is not a Draytek Vigor 3910 router, as this vulnerability only affects that specific model.
-
Check the firmware versionIn the router's web interface, navigate to System Maintenance > Firmware Upgrade or System Status > Router Information to locate the firmware version field. Compare the installed version against 4.3.2.6.Affected if The firmware version is exactly 4.3.2.6, as this is the only affected version listed.
-
Verify v2x00.cgi is present and accessibleAttempt to access the v2x00.cgi script via HTTP or HTTPS by entering the router's IP address followed by /cgi-bin/v2x00.cgi in a web browser. Observe whether the page loads or returns any response.Affected if The v2x00.cgi script is accessible and responds to requests, indicating the vulnerable component is exposed.
-
Confirm web interface is enabledIn the router's web interface, go to System Maintenance > Management or similar section to verify that the HTTP/HTTPS management interface is enabled and accessible from the network.Affected if The web management interface is enabled, as the buffer overflow occurs through the pub_key parameter in v2x00.cgi.
You are affected if you are running a Draytek Vigor 3910 router with firmware version exactly 4.3.2.6 and the v2x00.cgi web interface is accessible on your network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-provided firmware patch when available. In the interim, restrict access to the router's web management interface to trusted networks or IP addresses only to reduce attack surface.
- Consultation6.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46560 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-46560 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data