dbcve.org
Vigor3900 FirmwareOperating system · Draytek

CVE-2024-45884

HIGH · 8.0 CVSS v3.1 Published 2024-11-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
DrayTek Vigor3900 1.5.1.3 contains a post-authentication command injection vulnerability. This vulnerability occurs when the `action` parameter in `cgi-bin/mainfunction.cgi` is set to `setSWMGroup.`

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 confidence

DrayTek Vigor3900 version 1.5.1.3 contains a post-authentication command injection vulnerability in the web interface (cgi-bin/mainfunction.cgi). When the 'action' parameter is set to 'setSWMGroup', insufficient input validation allows an authenticated attacker to inject and execute arbitrary operating system commands on the device.

MitigationApply the vendor patch when available. In the interim, restrict network access to the device's web management interface to trusted IP addresses only and enforce strong authentication credentials to reduce the attack surface.

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
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 checks

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

  1. Identify the device model
    Access the device's web interface or check the device label/admin panel to confirm it is a DrayTek Vigor3900 router.
    Affected if The device is not a DrayTek Vigor3900, then it is not affected by this specific CVE.
  2. Check the firmware version
    Log into the web management interface and navigate to System Maintenance > Firmware Upgrade or similar section to view the installed firmware version. Alternatively, check the banner or status page for the version number.
    Affected if The installed firmware version is exactly 1.5.1.3, the device is affected.
  3. Verify the web interface is accessible
    Attempt to reach the device's web interface via HTTP or HTTPS on the default ports (typically 80 or 443). Confirm the cgi-bin/mainfunction.cgi endpoint exists by checking if the URL is responsive.
    Affected if The web interface is exposed and the device is running firmware 1.5.1.3, the vulnerability is present and could be exploited by an authenticated attacker.
  4. Confirm the vulnerable endpoint exists
    Check if the /cgi-bin/mainfunction.cgi endpoint is accessible on the device. This can be done by attempting a request to the URL (e.g., https://<device-ip>/cgi-bin/mainfunction.cgi).
    Affected if The endpoint exists and the firmware is 1.5.1.3, the command injection point is available.

A user is affected if they have a DrayTek Vigor3900 device running firmware version 1.5.1.3 with the web management interface accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch when available. In the interim, restrict network access to the device's web management interface to trusted IP addresses only and enforce strong authentication credentials to reduce the attack surface.

Recommended fix Moderate confidence

Latest Vigor3900 firmware version available from DrayTek (newer than 1.5.1.3)

  1. 1. Identify the current firmware version of the DrayTek Vigor3900 device by accessing the web administration interface or checking system status.
  2. 2. Check DrayTek's official support website (www.draytek.com) for firmware updates beyond version 1.5.1.3.
  3. 3. Download the latest stable firmware release from DrayTek's official download section for the Vigor3900 model.
  4. 4. Access the device's administration panel, navigate to the Firmware Upgrade section (typically under System Maintenance or Administration).
  5. 5. Upload and apply the new firmware file, ensuring the device remains powered on throughout the upgrade process.
  6. 6. After reboot, verify the new firmware version is installed and confirm the vulnerability is resolved.
Caveat Review DrayTek release notes for any configuration or feature changes between versions; backup device configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vigor3900 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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