GHSA-gv7f-5qqh-vxfx json
xous has unsound usages of `core::slice::from_raw_parts`
published last yr. modified last yr. also RUSTSEC-2024-0431
- 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
We consider `as_slice` and `as_slice_mut` unsound because: the pointer with any bit patterns could be cast to the slice of arbitrary types. The pointer could be created by unsafe new and deprecated `from_parts`. We consider that `from_parts` should be removed in latest version because it will help trigger unsoundness in `as_slice`. With new declared as unsafe, `as_slice` should also declared as unsafe.
This was patched in by marking two functions as `unsafe`.
Patch / fix
Is GHSA-gv7f-5qqh-vxfx 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 | xous | <0.9.51 >=0.0.0-0, <0.9.51 |
0.9.51 |
References
-
github.com
/betrusted-io/xous-core/pull/411
web
-
github.com
/betrusted-io/xous-core/issues/410
web, report
-
github.com
/betrusted-io/xous-core
package
-
rustsec.org
/advisories/RUSTSEC-2024-0431.html
web, advisory
-
crates.io
/crates/xous
package
Sources
- GitHub Advisory GHSA-gv7f-5qqh-vxfx
- OSV RUSTSEC-2024-0431
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.