dbcve.org
Vigor3910 FirmwareOperating system · Draytek

CVE-2024-46589

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 sIpv6AiccuUser parameter at inetipv6.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 within the inetipv6.cgi web script, specifically in the sIpv6AiccuUser parameter. Attackers can send specially crafted input that overflows a buffer, causing the device to crash and resulting in a Denial of Service.

MitigationApply vendor firmware updates when available; meanwhile, restrict access to the web management interface via network segmentation or firewall rules, and implement input validation/WAF protections for the affected endpoint.

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 router model
    Access the router web管理界面 or CLI and retrieve the device model information. Look for 'Vigor3910' or 'Vigor 3910' in the system status or device info page.
    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, navigate to System Maintenance > Firmware Upgrade or System Status to view the installed firmware version. Alternatively, use the CLI command 'sys show firmware' or similar to retrieve the version.
    Affected if The firmware version is exactly 4.3.2.6, then the device is vulnerable. Versions before or after this exact build may have different vulnerability status.
  3. Verify inetipv6.cgi is accessible
    Attempt to access the web script directly by browsing to the URL pattern: http://<router-ip>/cgi-bin/inetipv6.cgi or check if the script exists in the /cgi-bin/ directory via directory enumeration or by reviewing the router's published web endpoints.
    Affected if The inetipv6.cgi script is present and accessible on the device, indicating the web interface feature is enabled and potentially exploitable.
  4. Check if IPv6 ACCU feature is configured
    In the router web interface, navigate to IPv6 configuration settings or WAN settings to locate the 'IPv6 ACCU' or 'sIpv6AiccuUser' parameter configuration. This is typically found under IPv6 WAN setup or advanced IPv6 settings.
    Affected if The sIpv6AiccuUser parameter field exists and is configurable on the device, meaning the vulnerable input field is present and can be exploited with oversized input.

The device is affected only if it is a Draytek Vigor 3910 running exactly firmware version 4.3.2.6 with the inetipv6.cgi web script accessible and the IPv6 ACCU feature (sIpv6AiccuUser parameter) available in the configuration.

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 vendor firmware updates when available; meanwhile, restrict access to the web management interface via network segmentation or firewall rules, and implement input validation/WAF protections for the affected endpoint.

Fix this in Vigor3910 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-46589 — 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-46589 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