dbcve.org
Vigor2620 FirmwareOperating system · Draytek

CVE-2024-41594

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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
An issue in DrayTek Vigor310 devices through 4.3.2.6 allows an attacker to obtain sensitive information because the httpd server of the Vigor management UI uses a static string for seeding the PRNG of OpenSSL.

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

The DrayTek Vigor310 httpd server uses a static string to seed OpenSSL's PRNG, making cryptographic operations predictable. An attacker can exploit this weak seeding to potentially predict session tokens, authentication credentials, or encryption keys, leading to unauthorized access or information disclosure.

MitigationApply vendor firmware update when available; until then, restrict management interface access to trusted networks only and monitor for anomalous access patterns.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 DrayTek Vigor model
    Access the router's web administration interface or check the device label to determine the exact model number (e.g., Vigor2866, Vigor2765, etc.)
    Affected if The model is one of: Vigor2620, Vigor2915, Vigor2866, Vigor2766, Vigor2865, Vigor2765, Vigor2763, or Vigor2135
  2. Check the firmware version
    Log into the router web interface and navigate to System Status or Maintenance > Firmware Upgrade to view the installed firmware version
    Affected if The firmware version is lower than the patched version for your model (Vigor2620: any version, Vigor2915/Vigor2766/Vigor2765/Vigor2763/Vigor2135: < 4.4.5.3, Vigor2866/Vigor2865: < 4.4.5.2)
  3. Confirm httpd server is accessible
    Verify that the router's management web interface (httpd) is reachable from the network you are assessing (typically ports 80/443)
    Affected if The httpd server is exposed and the device model/firmware version falls within the affected ranges

You are affected if your DrayTek Vigor device model is in the affected list and your firmware version is below the patched threshold for that model, and the httpd management interface is 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
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 update when available; until then, restrict management interface access to trusted networks only and monitor for anomalous access patterns.

Recommended fix Moderate confidence

Firmware 4.4.5.3 (or 4.4.5.2 for Vigor2866/Vigor2865) - refer to DrayTek support for exact per-model releases

  1. 1. Identify the exact model number of your DrayTek device from the affected product list.
  2. 2. Check the current firmware version by accessing the device's web management interface or using the CLI.
  3. 3. Navigate to the DrayTek support website or firmware download page to obtain the appropriate fixed firmware.
  4. 4. For Vigor2915: upgrade to firmware version 4.4.5.3 or later.
  5. 5. For Vigor2866 and Vigor2865: upgrade to firmware version 4.4.5.2 or later.
  6. 6. For Vigor2766, Vigor2765, Vigor2763, and Vigor2135: upgrade to firmware version 4.4.5.3 or later.
  7. 7. For Vigor2620: contact DrayTek support for available firmware updates as no specific fixed version is listed.
  8. 8. Before upgrading, backup the device configuration.
Caveat Review release notes for any configuration changes or feature modifications between versions; backup configuration before upgrading

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

Fix this in Vigor2620 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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