RUSTSEC-2024-0408: Unsound usages of `std::slice::from_raw_parts`

What to do

1. See which version you have: cargo tree -i pprof (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p pprof. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example pprof = "0.14.0") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

The library breaks the safety assumptions when using unsafe API std::slice::from_raw_parts. First, when using the API in iterator implementation (TempFdArrayIterator.next), generic type could be any type, which would create and pass a misaligned pointer to the unsafe API. Second, when validating the address, the code passed the type c_void, which could also be any type, leading to potential uninitialized memory exposure.

Two unsound usages here highlight the necessity for developers to perform type checks before doing type conversion with unsafe API.

The panic caused by the misalignment causes several downstream applications (e.g., greptimedb) to crash when using pprof::report::ReportBuilder::build.

This was patched in 0.14.0.

The developer also suggested moving to pprof2.

References

• Package: crates.io/crates/pprof
• Advisory: rustsec.org/advisories/RUSTSEC-2024-0408.html
• Report: github.com/tikv/pprof-rs/issues/232
• Web: github.com/tikv/pprof-rs/pull/255

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.