Unratedcrates.ioPublished
fast-float2 has a segmentation fault due to lack of bound check
GHSA-jqcp-xc3v-f446
- Affected
- crates.io fast-float2 < 0.2.2
- Fixed in
- 0.2.2· Vendor fix available
- Issue
- In this case, the "fastfloat2::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.
Recommended action: Upgrade to 0.2.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.