MEDIUM
GHSA-jqcp-xc3v-f446
fast-float2 has a segmentation fault due to lack of bound check
Details
In this case, the "fast_float2::common::AsciiStr::first" method within the "AsciiStr" struct uses the unsafe keyword to reading from memory without performing bounds checking. Specifically, it directly dereferences a pointer offset by "self.ptr". Because of the above reason, the method accesses invalid memory address when it takes an empty string as its input. This approach violates Rust’s memory safety guarantees, as it can lead to invalid memory access if empty buffer is provided.
Are you affected?
Enter the version of the package you're using.
Affected packages
crates.io/fast-float2
Introduced in:
0Fixed in: 0.2.2Upgrade fast-float2 to 0.2.2 or newer (ecosystem crates.io).