dbcve.org
Vigor3900 FirmwareOperating system · Draytek

CVE-2024-51299

HIGH · 8.8 CVSS v3.1 Published 2024-10-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
In Draytek Vigor3900 1.5.1.3, attackers can inject malicious commands into mainfunction.cgi and execute arbitrary commands by calling the dumpSyslog function.

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

Command injection vulnerability in Draytek Vigor3900 firmware 1.5.1.3 allows remote attackers to inject and execute arbitrary OS commands via the dumpSyslog function in mainfunction.cgi. The lack of proper input sanitization on user-supplied parameters enables attackers to break out of expected command contexts and execute hostile commands on the underlying operating system.

MitigationApply vendor-supplied firmware patch when released; meanwhile restrict network access to the device management interface via ACLs or VPN, and monitor for suspicious mainfunction.cgi requests containing command operators.

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
Vigor3900 FirmwareOperating system
Affected:= 1.5.1.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify firmware version
    Access the device web interface and navigate to System Maintenance > Firmware Upgrade, or run 'show system-info' via CLI to confirm the installed firmware version is exactly 1.5.1.3
    Affected if Firmware version is 1.5.1.3
  2. Confirm mainfunction.cgi is accessible
    Attempt to access /cgi-bin/mainfunction.cgi on the device from an authorized management IP, or check HTTP server access logs for requests to this endpoint
    Affected if mainfunction.cgi is reachable over the network (HTTP/HTTPS)
  3. Check for dumpSyslog parameter usage
    Review access logs for mainfunction.cgi requests containing 'dumpSyslog' or 'action=dumpSyslog' query parameters, which trigger the vulnerable function
    Affected if Requests to mainfunction.cgi with dumpSyslog parameter are present in logs

You are affected if your Draytek Vigor3900 is running firmware version 1.5.1.3 and the mainfunction.cgi interface is exposed to network attackers.

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-supplied firmware patch when released; meanwhile restrict network access to the device management interface via ACLs or VPN, and monitor for suspicious mainfunction.cgi requests containing command operators.

Fix this in Vigor3900 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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 locally
dbcve dependency scanner

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