CyberSecBulletin
CVE-2024-8748NVD status: Analyzed

VMG8825-T50K firmware: Buffer Copy without Checking Size of Input

CVE-2024-8748 is a high-severity buffer copy without checking size of input vulnerability in VMG8825-T50K firmware from Zyxel, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected VMG8825-T50K firmware versions: <= V5.50(ABOM.8.4)C0; 5.50\(abom.8.4\)c0 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 0.52% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update nebula_nr5101_firmware to 1.16\(accg.0\)c0 or a later version.
  2. Update Ex3300-t0 Firmware to 5.50\(aby.5.4\)c0 or a later version.
  3. Update Ex3300-t1 Firmware to 5.50\(aby.5.4\)c0 or a later version.
  4. Read the advisory on zyxel.com for workarounds and exact fixed builds.
  5. 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
ZyxelVMG8825-T50K firmware<= V5.50(ABOM.8.4)C0; 5.50\(abom.8.4\)c0 and earlierNot stated
Zyxellte3301-plus_firmware1.00\(abqu.5\)c0 and earlierNot stated
Zyxellte5388-m804_firmware1.00\(absq.4\)c0 and earlierNot stated
Zyxellte5398-m904_firmware1.00\(abqv.4\)c0 and earlierNot stated
Zyxellte7480-m804_firmware1.00\(abra.9\)c0 and earlierNot stated
Zyxellte7490-m904_firmware1.00\(abqy.8\)c0 and earlierNot stated
Zyxelnr7101_firmware1.00\(abuv.10\)c0 and earlierNot stated
Zyxelnr7102_firmwarev1.00\(abyd.3\)c0 and earlierNot stated
Zyxelnebula_nr5101_firmwarebefore 1.16\(accg.0\)c01.16\(accg.0\)c0
Zyxelnebula_nr7101_firmware1.16\(accc.0\)c0 and earlierNot stated
Zyxelnebula_lte3301-plus_firmware1.18\(acca.4\)c0 and earlierNot stated
Zyxeldx3300-t0_firmware5.50\(abvy.5.3\)c0 and earlierNot stated
Zyxeldx3300-t1_firmware5.50(abvy.5.3)c0 and earlierNot stated
Zyxeldx3301-t0_firmware5.50\(abvy.5.3\)c0 and earlierNot stated
Zyxeldx4510-b0_firmware5.17\(abyl.7\)c0 and earlierNot stated
Zyxeldx4510-b1_firmware5.17\(abyl.7\)c0 and earlierNot stated
Zyxeldx5401-b0_firmware5.17\(abyo.6.3\)c0 and earlierNot stated
Zyxeldx5401_b1_firmware5.17\(abyo.6.3\)c0 and earlierNot stated
Zyxelee6510-10_firmware5.19\(acjq.0\)c0 and earlierNot stated
Zyxelex2210-t0_firmware5.50\(acdi.1\)c0 and earlierNot stated
Zyxelwx3100-t0_firmware5.50\(abvl.4.3\)c0 and earlierNot stated
Zyxelwx3401-b0_firmware5.17\(abve.2.5\)c0 and earlierNot stated
Zyxelwx3401-b1_firmware5.17(abve.2.5)c0 and earlierNot stated
Zyxelwx5600-t0_firmware5.70\(aceb.3.2\)c0 and earlierNot stated
Zyxelwx5610-b0_firmware5.18\(acgj.0\)c2 and earlierNot stated

Version data comes from the organisation that assigned the CVE; 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
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (zyxel.com.tw).

Official description

A buffer overflow vulnerability in the packet parser of the third-party library "libclinkc" in Zyxel VMG8825-T50K firmware versions through V5.50(ABOM.8.4)C0 could allow an attacker to cause a temporary denial of service (DoS) condition against the web management interface by sending a crafted HTTP POST request to a vulnerable device.

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. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in VMG8825-T50K firmware

All VMG8825-T50K firmware vulnerabilities

Recent Buffer Copy without Checking Size of Input vulnerabilities

Spotted an error? Tell us.