GHSA-x8jh-xj3x-gx3c `fast-float` has multiple soundness issues
Attackers can trigger undefined behavior and memory corruption in the unmaintained fast-float library, potentially leading to code execution or crashes.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is GHSA-x8jh-xj3x-gx3c?
GHSA-x8jh-xj3x-gx3c is a memory corruption vulnerability in fast-float, published on 31 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
fast-float contains multiple soundness issues:
- Undefined behavior when checking input length, which has been merged but no package pubished.
- Many functions marked as safe with non-local safety guarantees
The library is also unmaintained.
Alternatives
For quickly parsing floating-point numbers third-party crates are generally no longer needed. A fast float parsing algorithm by the author of lexical has been merged into libcore. When requiring direct parsing from bytes and/or partial parsers, the fast-float2 fork of fast-float containing these security patches and reduces overall usage of unsafe.
Which versions are affected by GHSA-x8jh-xj3x-gx3c?
3 open source packages ship an affected version, including fast-float.
| Package | Affected | Fixed in |
|---|---|---|
fast-float crates.io | All versions to 0.2.0 | None |
fast-float crates.io | All versions to 0.2.0 | None |
fast-float crates.io | From 0.0.0-0 | None |
How do I fix GHSA-x8jh-xj3x-gx3c?
No fix has been published for GHSA-x8jh-xj3x-gx3c yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is GHSA-x8jh-xj3x-gx3c being exploited?
There is no known exploitation of GHSA-x8jh-xj3x-gx3c in the wild and no public exploit code.
Sources
Also known as RUSTSEC-2024-0379.