GHSA-wm8x-php5-hvq6 json
Maligned causes incorrect deallocation
published 3y ago modified 3y ago also RUSTSEC-2023-0017
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
`maligned::align_first` manually allocates with an alignment larger than T, and then uses `Vec::from_raw_parts` on that allocation to get a `Vec<T>`.
[`GlobalAlloc::dealloc`](https://doc.rust-lang.org/std/alloc/trait.GlobalAlloc.html#tymethod.dealloc) requires that the `layout` argument must be the same layout that was used to allocate that block of memory.
When deallocating, `Box` and `Vec` may not respect the specified alignment and can cause undefined behavior.
Is GHSA-wm8x-php5-hvq6 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | maligned | <=0.2.1 >=0.0.0-0 |
no fix listed |
References
Sources
- GitHub Advisory GHSA-wm8x-php5-hvq6
- OSV RUSTSEC-2023-0017
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.