CyberSecBulletin
CVE-2022-32548NVD status: Modified

Vigor3910 Firmware: Buffer Copy without Checking Size of Input

CVE-2022-32548 is a critical-severity buffer copy without checking size of input vulnerability in Vigor3910 Firmware from DrayTek, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 4.3.1.1 as the first without the flaw, so updating Vigor3910 Firmware to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 34% chance of exploitation within 30 days, which is in the top 1.58% of all scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Vigor3910 Firmware to 4.3.1.1 or a later version.
  2. Update Vigor1000b Firmware to 4.3.1.1 or a later version.
  3. Update Vigor2962 Firmware to 4.3.1.1 or a later version.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
DraytekVigor3910 Firmwarebefore 4.3.1.14.3.1.1
DraytekVigor1000b Firmwarebefore 4.3.1.14.3.1.1
DraytekVigor2962 Firmwarebefore 4.3.1.14.3.1.1
DraytekVigor2962p Firmwarebefore 4.3.1.14.3.1.1
DraytekVigor2927 Firmwarebefore 4.4.04.4.0
DraytekVigor2927ax Firmwarebefore 4.4.04.4.0
DraytekVigor2927ac Firmwarebefore 4.4.04.4.0
DraytekVigor2927vac Firmwarebefore 4.4.04.4.0
DraytekVigor2927l Firmwarebefore 4.4.04.4.0
DraytekVigor2927lac Firmwarebefore 4.4.04.4.0
DraytekVigor2915 Firmwarebefore 4.3.3.24.3.3.2
DraytekVigor2915ac Firmwarebefore 4.3.3.24.3.3.2
DraytekVigor2952 Firmwarebefore 3.9.7.23.9.7.2
DraytekVigor2952p Firmwarebefore 3.9.7.23.9.7.2
DraytekVigor3220 Firmwarebefore 3.9.7.23.9.7.2
DraytekVigor2926 Firmwarebefore 3.9.8.13.9.8.1
DraytekVigor2926n Firmwarebefore 3.9.8.13.9.8.1
DraytekVigor2926ac Firmwarebefore 3.9.8.13.9.8.1
DraytekVigor2926vac Firmwarebefore 3.9.8.13.9.8.1
DraytekVigor2926l Firmwarebefore 3.9.8.13.9.8.1
DraytekVigor2926ln Firmwarebefore 3.9.8.13.9.8.1
DraytekVigor2926lac Firmwarebefore 3.9.8.13.9.8.1
DraytekVigor2862 Firmwarebefore 3.9.8.13.9.8.1
DraytekVigor2862n Firmwarebefore 3.9.8.13.9.8.1
DraytekVigor2862ac Firmwarebefore 3.9.8.13.9.8.1

Version data comes from NVD's product matching; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
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:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.110.0CriticalCNA (mitre.org)
CVSS 3.19.8CriticalNVD

Official description

An issue was discovered on certain DrayTek Vigor routers before July 2022 such as the Vigor3910 before 4.3.1.1. /cgi-bin/wlogin.cgi has a buffer overflow via the username or password to the aa or ab field.

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

The underlying weakness: Buffer Copy without Checking Size of Input

The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • 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.

More Buffer Copy without Checking Size of Input vulnerabilities (CWE-120)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Technical write-ups (may include proof of concept)

Other vulnerabilities in Vigor3910 Firmware

All Vigor3910 Firmware vulnerabilities

Recent Buffer Copy without Checking Size of Input vulnerabilities

Spotted an error? Tell us.