CVE-2024-38269: An improper restriction of operations within the bounds of a memory buffer in the USB file-sharing handler of the Zyxel VMG8825-T50K…
Noroxi assessment
Priority: Monitor (action score 19/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.43% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
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
An improper restriction of operations within the bounds of a memory buffer in the USB file-sharing handler of the Zyxel VMG8825-T50K firmware versions through 5.50(ABOM.8)C0 could allow an authenticated attacker with administrator privileges to cause potential memory corruptions, resulting in a thread crash on an affected device.
- Published
- Sep 23, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 37th percentile
- CWE
- CWE-119
Report tools
Action score
19
Low priority for now.
- CVSS
- 19 / 40 · 4.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Zyxel
- 4.9
- 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.
Is your version affected? Check itNoroxi 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 | wx5600-t0 firmware | cpe:2.3:o:zyxel:wx5600-t0_firmware |
| zyxel | wx5600-t0 | cpe:2.3:h:zyxel:wx5600-t0 |
| zyxel | wx3401-b0 firmware | cpe:2.3:o:zyxel:wx3401-b0_firmware |
| zyxel | wx3401-b0 | cpe:2.3:h:zyxel:wx3401-b0 |
| zyxel | wx3100-t0 firmware | cpe:2.3:o:zyxel:wx3100-t0_firmware |
| zyxel | wx3100-t0 | cpe:2.3:h:zyxel:wx3100-t0 |
| zyxel | scr50axe firmware | cpe:2.3:o:zyxel:scr50axe_firmware |
| zyxel | scr 50axe | cpe:2.3:h:zyxel:scr_50axe |
| zyxel | px3321-t1 firmware | cpe:2.3:o:zyxel:px3321-t1_firmware |
| zyxel | px3321-t1 | cpe:2.3:h:zyxel:px3321-t1 |
| zyxel | pm7300-t0 firmware | cpe:2.3:o:zyxel:pm7300-t0_firmware |
| zyxel | pm7300-t0 | cpe:2.3:h:zyxel:pm7300-t0 |
and 70 more
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
- <= 5.50(ABOM.8)C0affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- zyxel ax7501-b1 firmwarebefore 5.17\(abpc.5.2\)c0
- zyxel dx3300-t0 firmwarebefore 5.50\(abvy.5.3\)c0
- zyxel dx3300-t1 firmwarebefore 5.50\(abvy.5.3\)c0
- zyxel dx3301-t0 firmwarebefore 5.50\(abvy.5.3\)c0
- zyxel dx4510-b0 firmwarebefore 5.17\(abyl.7\)c0
- zyxel dx4510-b1 firmwarebefore 5.17\(abyl.7\)c0
- zyxel dx5401-b0 firmwarebefore 5.17\(abyo.6.2\)c0
- zyxel dx5401-b1 firmwarebefore 5.17\(abyo.6.2\)c0
- zyxel emg3525-t50b firmwarebefore 5.50\(abpm.9.2\)c0
- zyxel emg5523-t50b firmwarebefore 5.50\(abpm.9.2\)c0
- zyxel emg5723-t50k firmwarebefore 5.50\(abom.8.4\)c0
- zyxel ex3300-t0 firmwarebefore 5.50\(abvy.5.3\)c0
- zyxel ex3300-t1 firmwarebefore 5.50\(abvy.5.3\)c0
- zyxel ex3301-t0 firmwarebefore 5.50\(abvy.5.3\)c0
- zyxel ex3500-t0 firmwarebefore 5.44\(achr.2\)c0
- zyxel ex3501-t0 firmwarebefore 5.44\(achr.2\)c0
- zyxel ex3510-b0 firmwarebefore 5.17\(abup.12\)c0
- zyxel ex3510-b1 firmwarebefore 5.17\(abup.12\)c0
- zyxel ex3600-t0 firmwarebefore 5.70\(acif.0.3\)c0
- zyxel ex5401-b0 firmwarebefore 5.17\(abyo.6.2\)c0
Same product
zyxel: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-38268An improper restriction of operations within the bounds of a memory buffer in the MAC address parser of the Zyxel VMG8825-T50K firmware…19Monitor
- CVE-2024-38267An improper restriction of operations within the bounds of a memory buffer in the IPv6 address parser of the Zyxel VMG8825-T50K firmware…19Monitor
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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-382670 days apartAn improper restriction of operations within the bounds of a memory buffer in the IPv6 address parser of the Zyxel VMG8825-T50K firmware…19Monitor
- CVE-2024-382680 days apartAn improper restriction of operations within the bounds of a memory buffer in the MAC address parser of the Zyxel VMG8825-T50K firmware…19Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1534 · Sep 25, 2024(Zyxel VMG8825-T50K Güvenlik Bildirimi )
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
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
- Buffer ManipulationCAPEC-123likelihood: 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
ATT&CK techniques
—
Change log (0)
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.