fast-float2
Affected
- introduced
0.0.0-0, fixed0.2.2(semver)
Fixed versions
0.2.2
Fix
- Fixed version
0.2.2cargo update -p fast-float2 --precise 0.2.2
Advisory
Also known as: GHSA-jqcp-xc3v-f446
Segmentation fault due to lack of bound check
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.
Not rated by the source.
0.0.0-0, fixed 0.2.2 (semver)0.2.2
0.2.2cargo update -p fast-float2 --precise 0.2.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0