CVE-2024-46550
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 CGIbyFieldName parameter at chglog.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 CGIbyFieldName parameter of chglog.cgi on Draytek Vigor 3910 routers version 4.3.2.6. An attacker can send crafted input to trigger the overflow, causing denial of service.
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.
-
Confirm device model is Draytek Vigor 3910Access the router web interface or check the device label/model information to verify the hardware modelAffected if Device is not a Draytek Vigor 3910, then not affected by this specific CVE
-
Check installed firmware versionLog into the router administration panel and navigate to System Maintenance > Firmware Upgrade, or use the command line and run 'sysver' or 'cat /proc/version' to retrieve the firmware versionAffected if Firmware version is exactly 4.3.2.6, then the version matches the affected version listed in the CVE
-
Verify chglog.cgi endpoint exists and is accessibleAttempt to access the chglog.cgi file via HTTP/HTTPS request to the router (e.g., http://<router-ip>/chglog.cgi) using a web browser or curl commandAffected if The endpoint returns a response (200 OK) indicating the CGI script is present and accessible, meaning the vulnerable component is exposed
-
Check if CGIbyFieldName parameter can be sent to chglog.cgiSend a crafted GET or POST request to chglog.cgi with the CGIbyFieldName parameter (e.g., http://<router-ip>/chglog.cgi?CGIbyFieldName=test) and observe if the parameter is processedAffected if The router accepts and processes the CGIbyFieldName parameter without rejecting it, indicating the vulnerable parameter is enabled and the device could be exploited
If the device is a Draytek Vigor 3910 running firmware version 4.3.2.6 and the chglog.cgi endpoint with the CGIbyFieldName parameter is accessible, the environment is affected by this CVE.
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-supplied firmware patch when available; as interim measure, consider restricting access to the affected CGI endpoint via network segmentation or firewall rules.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46550 — 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-46550 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