GHSA-jqcp-xc3v-f446 — fast-float2
Fix: Alexhuszagh/fast-float-rust#7GHSA-jqcp-xc3v-f446 is a security vulnerability in fast-float2. A fix is available for fast-float2 — see the affected versions and patch details below.
fast-float2 has a segmentation fault due to lack of bound check
Real-World Exposure
fast-float2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | fast-float2 | all versions | 0.2.2cargo update -p fast-float2 --precise 0.2.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fast-float2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fast-float2 to 0.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jqcp-xc3v-f446 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jqcp-xc3v-f446 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-jqcp-xc3v-f446. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jqcp-xc3v-f446 in your dependencies?
O3 Security finds GHSA-jqcp-xc3v-f446 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.