CVE-2024-46590
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 ssidencrypt%d 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 confidenceBuffer overflow vulnerability in the ssidencrypt%d parameter of v2x00.cgi on Draytek Vigor 3910 firmware v4.3.2.6 allows remote attackers to cause Denial of Service via specially crafted input that exceeds expected buffer boundaries.
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 device modelAccess the device web interface or CLI and check the model name; look for 'Vigor3910' in the system information page or via 'show system-info' commandAffected if The device is not a Draytek Vigor 3910 (the vulnerability only affects this specific model)
-
Check the firmware versionIn the web interface, go to System Maintenance > Firmware Upgrade or use 'sys firmver' command via CLI; compare the version number to 4.3.2.6Affected if The firmware version is exactly 4.3.2.6 (this CVE affects only this specific version)
-
Verify v2x00.cgi is accessibleAttempt to access the v2x00.cgi script via HTTP/HTTPS on the device (e.g., https://<device_ip>/cgi-bin/v2x00.cgi); check if the endpoint respondsAffected if The v2x00.cgi script is reachable and responds to requests (this is the affected component)
-
Confirm wireless SSID configuration is presentIn the web interface, navigate to Wireless LAN > General or use CLI 'wlan ssid' command to list configured SSIDs; the ssidencrypt parameter relates to SSID encryption settingsAffected if Wireless SSIDs are configured on the device (the vulnerable parameter ssidencrypt%d controls encryption for wireless SSIDs)
-
Check for abnormal device behaviorReview device logs for crashes, restarts, or abnormal behavior around the web interface; check for signs of buffer overflow such as device reboots or service failuresAffected if The device exhibits unexpected crashes, reboots, or service interruptions that correlate with web interface access to the affected CGI script
The environment is affected if the device is a Draytek Vigor 3910 running firmware version 4.3.2.6, the v2x00.cgi web interface is accessible, and wireless SSIDs are configured, making the ssidencrypt%d parameter exploitable via specially crafted input.
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 vendor-provided firmware patch when available; until then, restrict access to the web management interface to trusted networks and implement input length validation on the affected parameter.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46590 — 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-46590 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