GHSA-jqcp-xc3v-f446
fast-float2 has a segmentation fault due to lack of bound check
GHSA-jqcp-xc3v-f446 is a vulnerability with no CVSS score yet in fast-float2, published January 13, 2025. No source lists public exploit code. Fixed in fast-float2 0.2.2.
- Severity
- UnratedNo CVSS score yet
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
0.2.2fast-float2 +1 more
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
| Package | Affected | Fixed |
|---|---|---|
fast-float2crates.io | before 0.2.2 | 0.2.2 |
fast-float2crates.io | 0.0.0-0 up to 0.2.2 | 0.2.2 |
What each source reports
GitHub AdvisoriesNo score
fast-float2 has a segmentation fault due to lack of bound check
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.
- Record
GHSA-jqcp-xc3v-f446- Updated
- 2026-11-02
OSVNo score
fast-float2 has a segmentation fault due to lack of bound check
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.
- Record
GHSA-jqcp-xc3v-f446- Updated
- 2026-11-02
OSVRUSTSEC-2025-0002No score
Segmentation fault due to lack of bound check
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.
- Record
RUSTSEC-2025-0002- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.