rust-zserio has Unbounded Memory Allocation
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-789.
Summary
### Impact When deserializing arrays, strings or bytes (blob) types zserio first reads the size of the variable, and then allocates sufficient memory to load data. Since the size is always trusted this can be abused by creating a data file with a large size value, causing the zserio runtime to allocate large amounts of memory. ### Patches Please cherry-pick [57f5fb](https://github.com/Danaozhong/rust-zserio/commit/57f5fb4a2a8611d58dbcc1a9221349206dd99c3c). ### Workarounds - Do not accept `zserio`-encoded messages from non-trusted sources. - Allocate a maximum heap amount to `rust-zerio` to avoid impacting other applications.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | rust-zserio (crates.io) | before 0.5.4 | 0.5.4 | Patch available | GHSA-fpf5-4jw8-67x8 |
- rust-zserio (crates.io) Vendor— Affected before 0.5.4 Fixed in 0.5.4 Patch available GHSA-fpf5-4jw8-67x8
Remediation
- Fix · GHSA-fpf5-4jw8-67x8 rust-zserio (crates.io) Fixed in 0.5.4 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-fpf5-4jw8-67x8
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences