GHSA-H7H7-6MX3-R89V
Fyrox has unsound usages of `Vec::from_raw_parts`
Overview
Description
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, 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 branch, but still not on the latest release (0.28.1).
Source: OX vulnerability database
Severity
LOW
No CVSS vector in the source. Severity comes from the advisory.
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Cargo (Rust) | fyrox-core | >=0.28.1, <0.36 | 0.36 |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- github.com https://github.com/FyroxEngine/Fyrox
- github.com https://github.com/FyroxEngine/Fyrox/commit/474e3b01a884366cdb7d704f7456ef692e992232
- github.com https://github.com/FyroxEngine/Fyrox/issues/630
- github.com https://github.com/FyroxEngine/Fyrox/pull/662
- rustsec.org https://rustsec.org/advisories/RUSTSEC-2024-0435.html
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.