dbcve.org
Vigor3910 FirmwareOperating system · Draytek

CVE-2024-46561

HIGH · 7.5 CVSS v3.1 Published 2024-09-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Draytek Vigor 3910 v4.3.2.6 was discovered to contain a buffer overflow in the queryret 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 confidence

A buffer overflow vulnerability exists in the Draytek Vigor 3910 router firmware v4.3.2.6 in the v2x00.cgi component. The vulnerability is triggered via the queryret parameter with specially crafted input, allowing an attacker to cause a Denial of Service by overflowing a buffer.

MitigationApply the vendor-supplied firmware patch when available. Until then, restrict access to the web management interface to trusted networks or IP addresses to reduce attack surface.

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
Vigor3910 FirmwareOperating system
Affected:= 4.3.2.6

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the router web interface or CLI and confirm the device is a Draytek Vigor 3910. This can typically be found in the web interface under System Status or via the CLI command 'sys info' or 'show system-info'.
    Affected if The device is not a Draytek Vigor 3910, then it is not affected by this specific CVE.
  2. Check the firmware version
    In the router web interface, go to System Maintenance > Firmware Upgrade or System Status to view the current firmware version. Alternatively, access the CLI and run 'vmss -c' or check the banner on login to display the firmware version.
    Affected if The firmware version is exactly 4.3.2.6, indicating the router is running the affected version.
  3. Verify v2x00.cgi is accessible
    Attempt to access the v2x00.cgi endpoint on the router. This is typically found at https://[router-ip]/cgi/v2x00.cgi. Check if the web server responds to this CGI script.
    Affected if The v2x00.cgi script is not present or not accessible, the specific attack vector may not be available.
  4. Confirm web management interface is enabled
    Check if the HTTP/HTTPS web management interface is enabled on the router. This can be verified in System Maintenance > Management or via CLI. The vulnerability requires the web interface to be accessible.
    Affected if The web management interface is disabled or only available via specific IP restrictions, the attack surface is reduced.
  5. Inspect network exposure
    Determine if the router web interface is exposed to untrusted networks. Check the access control settings in System Maintenance > Management to see if management access is limited to LAN or specific IP ranges.
    Affected if The web management interface is exposed to the internet or untrusted networks, making it potentially vulnerable to remote exploitation.

A user is affected if they are running Draytek Vigor 3910 firmware version exactly 4.3.2.6 and the v2x00.cgi web interface component is accessible to the attacker.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied firmware patch when available. Until then, restrict access to the web management interface to trusted networks or IP addresses to reduce attack surface.

Fix this in Vigor3910 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-46561 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-46561 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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