CVE-2024-46316
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 Vigor3900 v1.5.1.6 was discovered to contain a command injection vulnerability via the sub_2C920 function at /cgi-bin/mainfunction.cgi. This vulnerability allows attackers to execute arbitrary commands via supplying a crafted HTTP message.
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 confidenceCommand injection vulnerability in DrayTek Vigor3900 v1.5.1.6 in the sub_2C920 function within /cgi-bin/mainfunction.cgi. Attackers can execute arbitrary operating system commands by sending crafted HTTP messages to the web interface.
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= 1.5.1.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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 check the device label/marketing materials to confirm it is a DrayTek Vigor3900 device.Affected if The device is not a DrayTek Vigor3900 (not affected)
-
Check the installed firmware versionLog into the router web interface and navigate to System Maintenance > Firmware Upgrade, or use the command line to retrieve the firmware version. Compare the version number to 1.5.1.6.Affected if The firmware version is exactly 1.5.1.6 (directly affected)
-
Verify the web interface is accessibleAttempt to access the URL http://[device-ip]/cgi-bin/mainfunction.cgi in a web browser or via curl. A successful HTTP response indicates the CGI endpoint is reachable.Affected if The mainfunction.cgi endpoint responds, meaning the management web interface is exposed on the network
-
Confirm remote management is enabledCheck the router's configuration under System Maintenance > Access Control or similar to see if the web interface is enabled for remote (WAN) access. Inspect firewall rules to determine if external hosts can reach the CGI endpoint.Affected if Remote management is enabled or the web interface is accessible from untrusted networks, increasing exposure to the vulnerability
The environment is affected if it is a DrayTek Vigor3900 running firmware version 1.5.1.6 with the web interface (specifically /cgi-bin/mainfunction.cgi) accessible to the attacker.
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 firmware patch when available. Until patched, restrict access to the management interface via network segmentation or firewall rules to prevent unauthorized attackers from reaching the CGI endpoint.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46316 — 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-46316 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