CyberSecBulletin
CVE-2024-41592NVD status: Analyzed

vigor3910_firmware: Stack-based Buffer Overflow

Published Updated By the CyberSecBulletin desk

CVE-2024-41592 is a high-severity stack-based buffer overflow vulnerability in vigor3910_firmware from DrayTek, with a CVSS 3.1 base score of 8.0 out of 10. It can be exploited from the same local network by an attacker with a low-privileged account, without any action from a user. Affected vigor3910_firmware versions: 4.3.2.6 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.4% chance of exploitation within 30 days, higher than 73% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Vigor2952 Firmware to 3.9.8.2 or a later version.
  2. Update Vigor2620 Firmware to 3.9.8.9 or a later version.
  3. Update Vigor2915 Firmware to 4.4.5.3 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
Draytekvigor3910_firmware4.3.2.6 and earlierNot stated
DraytekVigor2952 Firmwarebefore 3.9.8.23.9.8.2
DraytekVigor2620 Firmwarebefore 3.9.8.93.9.8.9
DraytekVigor2915 Firmwarebefore 4.4.5.34.4.5.3
DraytekVigor2866 Firmwarebefore 4.4.5.24.4.5.2
DraytekVigor2766 Firmwarebefore 4.4.5.34.4.5.3
DraytekVigor2865 Firmwarebefore 4.4.5.24.4.5.2
DraytekVigor2765 Firmwarebefore 4.4.5.34.4.5.3
DraytekVigor2763 Firmwarebefore 4.4.5.34.4.5.3
DraytekVigor2135 Firmwarebefore 4.4.5.34.4.5.3
DraytekVigor166 Firmwarebefore 4.2.74.2.7
DraytekVigor3912 Firmwarebefore 4.3.6.14.3.6.1
DraytekVigor1000b Firmwarebefore 4.3.2.8; 4.4.0.0 up to, but not including, 4.4.3.14.3.2.8, 4.4.3.1
DraytekVigor165 Firmwarebefore 4.2.74.2.7
DraytekVigor2962 Firmwarebefore 4.3.2.8; 4.4.0.0 up to, but not including, 4.4.3.14.3.2.8, 4.4.3.1
DraytekVigorlte200 Firmwarebefore 3.9.8.93.9.8.9
DraytekVigor2133 Firmwarebefore 3.9.93.9.9
DraytekVigor2762 Firmwarebefore 3.9.93.9.9
DraytekVigor2832 Firmwarebefore 3.9.93.9.9
DraytekVigor2860 Firmwarebefore 3.9.83.9.8
DraytekVigor2862 Firmwarebefore 3.9.9.53.9.9.5
DraytekVigor2925 Firmwarebefore 3.9.83.9.8
DraytekVigor2926 Firmwarebefore 3.9.9.53.9.9.5
DraytekVigor3220 Firmwarebefore 3.9.8.23.9.8.2

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).

Official description

DrayTek Vigor3910 devices through 4.3.2.6 have a stack-based overflow when processing query string parameters because GetCGI mishandles extraneous ampersand characters and long key-value pairs.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Stack-based Buffer Overflow

The product writes past the end of a buffer that was allocated on the stack.

How developers prevent this class of flaw

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
  • Use an abstraction library to abstract away risky APIs. Not a complete solution.
  • Implement and perform bounds checking on input.

More Stack-based Buffer Overflow vulnerabilities (CWE-121)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Other vulnerabilities in vigor3910_firmware

All vigor3910_firmware vulnerabilities

Recent Stack-based Buffer Overflow vulnerabilities

Spotted an error? Tell us.