fast-float2 has a segmentation fault due to lack of bound check
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | fast-float2 (crates.io) | before 0.2.2 | 0.2.2 | Patch available | GHSA-jqcp-xc3v-f446 |
- fast-float2 (crates.io) Vendor— Affected before 0.2.2 Fixed in 0.2.2 Patch available GHSA-jqcp-xc3v-f446
Remediation
- Fix · GHSA-jqcp-xc3v-f446 fast-float2 (crates.io) Fixed in 0.2.2 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-jqcp-xc3v-f446
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences