dbcve.org
Vigor2620 FirmwareOperating system · Draytek

CVE-2024-41588

HIGH · 8.0 CVSS v3.1 Published 2024-10-03
Fix available
A fix is available. Upgrade to 4.4.5.2 / 4.4.5.3 or later.
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
The CGI endpoints v2x00.cgi and cgiwcg.cgi of DrayTek Vigor3910 devices through 4.3.2.6 are vulnerable to buffer overflows, by authenticated users, because of missing bounds checking on parameters passed through POST requests to the strncpy 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 · high confidence

Buffer overflow vulnerability in DrayTek Vigor3910 devices allows authenticated users to overflow buffers in CGI endpoints v2x00.cgi and cgiwcg.cgi via POST requests. The root cause is missing bounds checking on parameters before they are passed to the strncpy function, allowing data to exceed buffer boundaries.

MitigationApply vendor firmware updates when available. As an interim control, restrict access to these CGI endpoints to trusted authenticated users only, or disable the affected CGI handlers if not required.

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
Vigor2620 FirmwareOperating system
Affected:all versions
Vigor2915 FirmwareOperating system
Affected:< 4.4.5.3
Vigor2866 FirmwareOperating system
Affected:< 4.4.5.2
Vigor2766 FirmwareOperating system
Affected:< 4.4.5.3
Vigor2865 FirmwareOperating system
Affected:< 4.4.5.2
Vigor2765 FirmwareOperating system
Affected:< 4.4.5.3
Vigor2763 FirmwareOperating system
Affected:< 4.4.5.3
Vigor2135 FirmwareOperating system
Affected:< 4.4.5.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 DrayTek Vigor model
    Access the device web interface or check the device label/menu to confirm the exact model number (e.g., Vigor3910, Vigor2866, Vigor2915, etc.)
    Affected if The device is one of the listed affected models: Vigor2620, Vigor2915, Vigor2866, Vigor2766, Vigor2865, Vigor2765, Vigor2763, or Vigor2135
  2. Check installed firmware version
    Navigate to the device web interface System Maintenance > Firmware Upgrade or similar menu to view the current firmware version. Alternatively, check via CLI if available.
    Affected if The firmware version is lower than the patched version for your model: Vigor2915/Vigor2766/Vigor2765/Vigor2763/Vigor2135 < 4.4.5.3, Vigor2866/Vigor2865 < 4.4.5.2, or Vigor2620 at any version
  3. Verify CGI endpoint accessibility
    Attempt to access or probe the URLs /cgi/v2x00.cgi and /cgi/cgiwcg.cgi on the device (e.g., https://device-ip/cgi/v2x00.cgi) to confirm these endpoints exist and respond.
    Affected if The CGI endpoints respond to requests, indicating they are enabled and accessible
  4. Confirm remote management is enabled
    Check the device configuration under Remote Management, Web UI Access, or CGI Handler settings to see if web-based management and CGI endpoints are enabled for network access.
    Affected if Remote management or web UI access is enabled, allowing unauthenticated or authenticated users to reach the CGI endpoints from the network
  5. Review authentication settings
    Check the device user authentication configuration to determine whether strong password policies are in place and if the CGI endpoints can be accessed by all authenticated users.
    Affected if The device relies on authentication for CGI access but does not restrict specific users from reaching the vulnerable endpoints, or if default/simple credentials may be in use

The environment is affected if the device is a DrayTek Vigor model listed in the affected products with a firmware version below the patched threshold and the CGI endpoints (v2x00.cgi, cgiwcg.cgi) are accessible either locally or remotely.

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
Upgrade available Upgrade to 4.4.5.2 / 4.4.5.3 or later
Fixed in 4.4.5.24.4.5.3
Interim mitigation

Apply vendor firmware updates when available. As an interim control, restrict access to these CGI endpoints to trusted authenticated users only, or disable the affected CGI handlers if not required.

Recommended fix Moderate confidence

Firmware 4.4.5.3 (or 4.4.5.2 for Vigor2866/Vigor2865) depending on model

  1. Identify the specific DrayTek Vigor model from the affected list (Vigor2620, Vigor2915, Vigor2866, Vigor2766, Vigor2865, Vigor2765, Vigor2763, or Vigor2135)
  2. Access the device administration interface or DrayTek support portal to download firmware
  3. Download the appropriate firmware version: For Vigor2915, Vigor2766, Vigor2765, Vigor2763, Vigor2135 upgrade to firmware version 4.4.5.3 or later; For Vigor2866, Vigor2865 upgrade to firmware version 4.4.5.2 or later
  4. Backup current device configuration before applying firmware update
  5. Upload and install the new firmware through the device's web interface or TFTP method
  6. Verify the firmware installation was successful and the device is operational
  7. Confirm the vulnerability is remediated by ensuring the CGI endpoints v2x00.cgi and cgiwcg.cgi now properly validate input lengths before passing to strncpy
Caveat Standard firmware upgrade risks apply - ensure backup of configuration before proceeding; some legacy settings may not be preserved

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

Fix this in Vigor2620 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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