GHSA-8655-xgh5-5vvq fast-fault has a segmentation fault due to lack of bound check

Not scored Published

An attacker can cause a segmentation fault and denial of service by providing an empty string to the fast-float library due to missing bounds checks.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Not stated
Victim action needed
Not needed
Fix
None listed

What is GHSA-8655-xgh5-5vvq?

GHSA-8655-xgh5-5vvq is a memory corruption vulnerability in fast-float, published on 13 Jan 2025.

Official description

In this case, the "fast_float::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.

No patched version for fast-float crate has been released, but a patch is available in the fast-float2 fork.

Which versions are affected by GHSA-8655-xgh5-5vvq?

3 open source packages ship an affected version, including fast-float.

PackageAffectedFixed in
fast-float crates.ioAll versions to 0.2.0None
fast-float crates.ioAll versions to 0.2.0None
fast-float crates.ioFrom 0.0.0-0None

How do I fix GHSA-8655-xgh5-5vvq?

No fix has been published for GHSA-8655-xgh5-5vvq 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-8655-xgh5-5vvq being exploited?

There is no known exploitation of GHSA-8655-xgh5-5vvq in the wild and no public exploit code.

Sources

Also known as RUSTSEC-2025-0003.

Is GHSA-8655-xgh5-5vvq in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free