RUSTSEC-2021-0123: Converting `NSString` to a String Truncates at Null Bytes

What to do

1. See which version you have: cargo tree -i fruity (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p fruity. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example fruity = "0.3.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

Methods of NSString for conversion to a string may return a partial result. Since they call CStr::from_ptr on a pointer to the string buffer, the string is terminated at the first null byte, which might not be the end of the string.

In addition to the vulnerable functions listed for this issue, the implementations of Display, PartialEq, PartialOrd, and ToString for NSString are also affected, since they call those functions.

Impact

Since NSString is commonly used as the type for paths by the Foundation framework, null byte truncation might allow for easily bypassing file extension checks. For example, if a file name is provided by a user and validated to have one of a specific set of extensions, with validation taking place before truncation, an attacker can add an accepted extension after a null byte (e.g., file.exe\0.txt). After truncation, the file name used by the application would be file.exe.

It would be better to generate unique names for files, instead of using user-provided names, but not all applications take this approach.

Example:

let string = NSString::from_str("null\0byte");
println!("{}", string);

That example only prints the string "null".

References

• Package: crates.io/crates/fruity
• Advisory: rustsec.org/advisories/RUSTSEC-2021-0123.html
• Report: github.com/nvzqz/fruity/issues/14

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