CVE-2024-46592
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_5g%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 · high confidenceA buffer overflow vulnerability exists in the Draytek Vigor 3910 router firmware v4.3.2.6 within the v2x00.cgi web interface. The ssidencrypt_5g%d parameter fails to properly validate input length before copying to a fixed-size buffer, allowing remote attackers to trigger a Denial of Service by sending specially crafted input that overflows the allocated buffer.
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 router's web interface or CLI and confirm the device model is Draytek Vigor 3910. This can typically be found in the web UI footer or via the 'sys info' command in CLI.Affected if The device is not a Draytek Vigor 3910 router, then this CVE does not apply.
-
Check the installed firmware versionIn the router's web interface, navigate to System Maintenance > Firmware Upgrade or check the status page to view the current firmware version. Alternatively, use the CLI command 'sys fw' or 'version' to retrieve the firmware version.Affected if The firmware version is 4.3.2.6, the specific version listed as affected by this CVE.
-
Verify v2x00.cgi is accessibleAttempt to access the v2x00.cgi endpoint on the router's web interface. The URL typically follows the pattern https://[router-ip]/cgi-bin/v2x00.cgi. Check if the endpoint responds or is reachable.Affected if The v2x00.cgi web interface is exposed and reachable on the network, making the vulnerable parameter accessible.
-
Confirm ssidencrypt_5g parameter exposureThe vulnerable parameter ssidencrypt_5g%d is part of the wireless settings in the v2x00.cgi interface. Check if wireless configuration pages for 5GHz networks are accessible or exposed in the router's web UI.Affected if The wireless configuration interface (specifically 5GHz settings) using v2x00.cgi is accessible, meaning the vulnerable ssidencrypt_5g%d parameter can be reached.
You are affected if you have a Draytek Vigor 3910 router running firmware version 4.3.2.6 with the v2x00.cgi web interface and its 5GHz wireless settings 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-supplied firmware patch when available; until then, restrict access to the router's web management interface to trusted networks or IP addresses to reduce the attack surface.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46592 — 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-46592 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