CVE-2024-8748: A buffer overflow vulnerability in the packet parser of the third-party library "libclinkc" in Zyxel VMG8825-T50K firmware versions through
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.52% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 2, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 44th percentile
- CWE
- CWE-120
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Zyxel
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| zyxel | lte3301-plus firmware | cpe:2.3:o:zyxel:lte3301-plus_firmware |
| zyxel | lte3301-plus | cpe:2.3:h:zyxel:lte3301-plus |
| zyxel | lte5388-m804 firmware | cpe:2.3:o:zyxel:lte5388-m804_firmware |
| zyxel | lte5388-m804 | cpe:2.3:h:zyxel:lte5388-m804 |
| zyxel | lte5398-m904 firmware | cpe:2.3:o:zyxel:lte5398-m904_firmware |
| zyxel | lte5398-m904 | cpe:2.3:h:zyxel:lte5398-m904 |
| zyxel | lte7480-m804 firmware | cpe:2.3:o:zyxel:lte7480-m804_firmware |
| zyxel | lte7480-m804 | cpe:2.3:h:zyxel:lte7480-m804 |
| zyxel | lte7490-m904 firmware | cpe:2.3:o:zyxel:lte7490-m904_firmware |
| zyxel | lte7490-m904 | cpe:2.3:h:zyxel:lte7490-m904 |
| zyxel | nr7101 firmware | cpe:2.3:o:zyxel:nr7101_firmware |
| zyxel | nr7101 | cpe:2.3:h:zyxel:nr7101 |
and 114 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- zyxel ax7501-b0 firmwarebefore 5.17\(abpc.5.3\)c0
- zyxel ax7501-b1 firmwarebefore 5.17\(abpc.5.3\)c0
- zyxel dx3300-t0 firmwarebefore 5.50\(aby.5.4\)c0
- zyxel dx3300-t1 firmwarebefore 5.50\(aby.5.4\)c0
- zyxel dx3301-t0 firmwarebefore 5.50\(aby.5.4\)c0
- zyxel dx4510-b0 firmwarebefore 5.17\(abyl.8\)c0
- zyxel dx4510-b1 firmwarebefore 5.17\(abyl.8\)c0
- zyxel dx5401-b0 firmwarebefore 5.17\(abyo.6.4\)c0
- zyxel dx5401-b1 firmwarebefore 5.17\(abyo.6.4\)c0
- zyxel ee6510-10 firmwarebefore 5.19\(acjq.1\)c0
- zyxel emg3525-t50b firmwarebefore 5.50\(abpm.9.3\)c0
- zyxel emg5523-t50b firmwarebefore 5.50\(abpm.9.3\)c0
- zyxel emg5723-t50k firmwarebefore 5.50\(abom.8.5\)c0
- zyxel emg6726-b10a firmwarebefore 5.13\(abnp.8\)c1
- zyxel ex2210-t0 firmwarebefore 5.50\(acdi.2\)c0
- zyxel ex3300-t0 firmwarebefore 5.50\(aby.5.4\)c0
- zyxel ex3300-t1 firmwarebefore 5.50\(aby.5.4\)c0
- zyxel ex3301-t0 firmwarebefore 5.50\(aby.5.4\)c0
- zyxel ex3500-t0 firmwarebefore 5.44\(achr.3\)c0
- zyxel ex3501-t0 firmwarebefore 5.44\(achr.3\)c0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Zyxel). Independent of NVD's CPE analysis and usually ahead of it.
Zyxel VMG8825-T50K firmware
- <= V5.50(ABOM.8.4)C0affected
Same product
zyxel: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-6599An uncontrolled resource consumption vulnerability in the web server of Zyxel DX3301-T0 firmware version 5.50(ABVY.6.3)C0 and earlier could 30Monitor
- CVE-2022-43392A buffer overflow vulnerability in the parameter of web server in Zyxel NR7101 firmware prior to V1.15(ACCC.3)C0, which could allow an authe26Monitor
- CVE-2022-43391A buffer overflow vulnerability in the parameter of the CGI program in Zyxel NR7101 firmware prior to V1.15(ACCC.3)C0, which could allow an 26Monitor
Published before and after this one in the same product
- Later →CVE-2025-11845Feb 23, 2026 · A null pointer dereference vulnerability in the certificate downloader CGI program of the Zyxel VMG3625-T50B firmware versions through 5.50(19Monitor
- Later →CVE-2025-11846Feb 23, 2026 · A null pointer dereference vulnerability in the account settings CGI program of the Zyxel VMG3625-T50B firmware versions through 5.50(ABPM.919Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.