Advisory

RUSTSEC-2025-0002

Also known as: GHSA-jqcp-xc3v-f446

Summary

Segmentation fault due to lack of bound check

Details

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.

Severity

Not rated by the source.

Dates

Published
2025-01-13 12:00 UTC
Modified
2025-10-28 06:29 UTC

Affected packages and fixes

fast-float2

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.2.2 (semver)

Fixed versions

0.2.2

Fix

  • Fixed version 0.2.2
    cargo update -p fast-float2 --precise 0.2.2

Fix 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

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences