RUSTSEC-2024-0377: Heap Buffer overflow using c_chars_to_str function

What to do

1. See which version you have: cargo tree -i dbn (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p dbn. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example dbn = "0.22.1") 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 heap-buffer-overflow is triggered in the strlen() function when handling the c_chars_to_str function in the dbn crate. This vulnerability occurs because the CStr::from_ptr() function in Rust assumes that the provided C string is null-terminated. However, there is no guarantee that the input chars array passed to the c_chars_to_str function is properly null-terminated.

If the chars array does not contain a null byte (\0), strlen() will continue to read beyond the bounds of the buffer in search of a null terminator. This results in an out-of-bounds memory read and can lead to a heap-buffer-overflow, potentially causing memory corruption or exposing sensitive information.

References

• Package: crates.io/crates/dbn
• Advisory: rustsec.org/advisories/RUSTSEC-2024-0377.html
• Report: github.com/databento/dbn/issues/67

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