Fyrox has unsound usages of `Vec::from_raw_parts`
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
The library provides a public safe API `transmute_vec_as_bytes`, which incorrectly assumes that any generic type `T` could have stable layout, causing to uninitialized memory exposure if the users pass any types with padding bytes as `T` and cast it to `u8` pointer. In the [issue](https://github.com/FyroxEngine/Fyrox/issues/630), we develop a PoC to show passing struct type to `transmute_vec_as_bytes` could lead to undefined behavior with `Vec::from_raw_parts`. The developers provide a patch by changing trait of `Copy` to `Pod`, which can make sure `T` should be plain data. This was patched in the latest version of [master](https://github.com/FyroxEngine/Fyrox/blob/3f9ad6f9667047dac051b0e97d544e5b38e5ae72/fyrox-core/src/lib.rs#L351-L360) branch, but still not on the latest release (0.28.1).
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 |
|---|---|---|---|---|---|
| — | fyrox-core (crates.io) | 0.28.1 to before 0.36 | 0.36 | Patch available | GHSA-h7h7-6mx3-r89v |
- fyrox-core (crates.io) Vendor— Affected 0.28.1 to before 0.36 Fixed in 0.36 Patch available GHSA-h7h7-6mx3-r89v
Remediation
- Fix · GHSA-h7h7-6mx3-r89v fyrox-core (crates.io) Fixed in 0.36 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-h7h7-6mx3-r89v
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences