dbcve.org
Nebula Lte3301 Plus FirmwareOperating system · Zyxel

CVE-2024-5412

HIGH · 7.5 CVSS v3.1 Published 2024-09-03
Fix available
A fix is available. Upgrade to 1.10 / 1.18 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
A buffer overflow vulnerability in the library "libclinkc" of the Zyxel VMG8825-T50K firmware version 5.50(ABOM.8)C0 could allow an unauthenticated attacker to cause denial of service (DoS) conditions by sending a crafted HTTP request to a vulnerable device.

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 · moderate confidence

Buffer overflow vulnerability in the libclinkc library of Zyxel VMG8825-T50K routers running firmware version 5.50(ABOM.8)C0. An unauthenticated attacker can send a specially crafted HTTP request that overflows a buffer, causing the device to crash and resulting in denial of service.

MitigationApply vendor firmware update when available; as interim measure, implement network-level filtering or segmentation to limit exposure to unauthenticated HTTP requests targeting the vulnerable service.

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
Nebula Lte3301 Plus FirmwareOperating system
Affected:< 1.18\(acca.4\)c0
Nebula Fwa505 FirmwareOperating system
Affected:< 1.18\(acko.4\)c0
Nebula Fwa710 FirmwareOperating system
Affected:< 1.18\(acgc.4\)c0
Nebula Fwa510 FirmwareOperating system
Affected:< 1.18\(acgd.4\)c0
Wx5600 T0 FirmwareOperating system
Affected:< 5.70\(aceb.3.2\)c0
Wx3401 B0 FirmwareOperating system
Affected:< 5.17\(abve.2.5\)c0
Wx3100 T0 FirmwareOperating system
Affected:< 5.50\(abvl.4.2\)c0
Scr50axe FirmwareOperating system
Affected:< 1.10\(acgn.3\)c0

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device model
    Access the router web interface or use SNMP/CLI to retrieve the device model name. Check if the model is VMG8825-T50K, LTE3301 Plus, FWA505, FWA710, FWA510, WX5600 T0, WX3401 B0, WX3100 T0, or SCR50AXE.
    Affected if Device model matches one of the listed affected models.
  2. Check firmware version
    Navigate to the router admin panel status or system info page, or use CLI command 'show version' or 'router-info' to retrieve the firmware version string.
    Affected if Firmware version is lower than the threshold for your model (LTE3301 Plus < 1.18(acca.4)c0, FWA505 < 1.18(acko.4)c0, FWA710 < 1.18(acgc.4)c0, FWA510 < 1.18(acgd.4)c0, WX5600 T0 < 5.70(aceb.3.2)c0, WX3401 B0 < 5.17(abve.2.5)c0, WX3100 T0 < 5.50(abvl.4.2)c0, SCR50AXE < 1.10(acgn.3)c0, or VMG8825-T50K
  3. Verify libclinkc library presence
    If you have CLI or SSH access, check for the presence of libclinkc library on the device filesystem, typically located in /lib or /usr/lib directories.
    Affected if The libclinkc library file exists on the device.
  4. Assess HTTP service exposure
    Scan the device IP from an external network perspective using 'nmap -p 80,443 <device-ip>' or check router port forwarding / firewall rules to determine if the HTTP management interface is reachable from WAN/untrusted networks.
    Affected if HTTP service (port 80/443) is exposed to unauthenticated network access.
  5. Review system logs for crashes
    Check router system logs (via web UI under Status > Logs or CLI command 'logread' or 'show logs') for recent crash reports, kernel panics, or unexpected reboots occurring around the time of suspected exploitation attempts.
    Affected if Logs show unexplained crashes, buffer overflow errors, or sudden reboots matching the DoS behavior described.

Device is affected if it is a Zyxel model from the affected list, runs a firmware version below the specified threshold, and has the libclinkc library present with HTTP service network exposure.

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 1.10 / 1.18 / 5.17 or later
Fixed in 1.101.185.17
Interim mitigation

Apply vendor firmware update when available; as interim measure, implement network-level filtering or segmentation to limit exposure to unauthenticated HTTP requests targeting the vulnerable service.

Recommended fix High confidence

Nebula Lte3301 Plus: 1.18(acca.4)c0 or later | Nebula Fwa505: 1.18(acko.4)c0 or later | Nebula Fwa710: 1.18(acgc.4)c0 or later | Nebula Fwa510: 1.18(acgd.4)c0 or later | Wx5600 T0: 5.70(aceb.3.2)c0 or later | Wx3401 B0: 5.17(abve.2.5)c0 or later | Wx3100 T0: 5.50(abvl.4.2)c0 or later | Scr50axe: 1.1

  1. 1. Identify the exact model number of your Zyxel device from the affected list (Nebula Lte3301 Plus, Nebula Fwa505, Nebula Fwa710, Nebula Fwa510, Wx5600 T0, Wx3401 B0, Wx3100 T0, or Scr50axe)
  2. 2. Navigate to Zyxel's official support page at www.zyxel.com and locate the firmware download section for your specific device model
  3. 3. Download the latest firmware version that meets or exceeds the fixed release for your device: Nebula models require 1.18 or higher, Wx5600 T0 requires 5.70 or higher, Wx3401 B0 requires 5.17 or higher, Wx3100 T0 requires 5.50 or higher, Scr50axe requires 1.10 or higher
  4. 4. Access the device's web-based management interface or admin console
  5. 5. Locate the firmware upgrade section (typically under Administration, Maintenance, or System settings)
  6. 6. Upload the downloaded firmware file and initiate the upgrade process
  7. 7. Wait for the device to complete the firmware update and reboot automatically
  8. 8. After reboot, verify the firmware version in the device administration panel to confirm successful installation
Caveat Firmware upgrades may reset device configuration to defaults; backup current configuration before upgrading and re-apply settings after upgrade if necessary

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

Fix this in Nebula Lte3301 Plus Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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