# GHSA-jqcp-xc3v-f446: fast-float2 has a segmentation fault due to lack of bound check

> An attacker can cause a segmentation fault and application crash by providing an empty string to the fast-float2 library due to missing bounds checks.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jan 2025
- **Also known as:** RUSTSEC-2025-0002

## What is GHSA-jqcp-xc3v-f446?

GHSA-jqcp-xc3v-f446 is a memory corruption vulnerability in fast-float2, published on 13 Jan 2025. 

### Official 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.

## Which versions are affected by GHSA-jqcp-xc3v-f446?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fast-float2` | crates.io | All versions | 0.2.2 |
| `fast-float2` | crates.io | All versions | 0.2.2 |
| `fast-float2` | crates.io | From 0.0.0-0 | 0.2.2 |

## How do I fix GHSA-jqcp-xc3v-f446?

Upgrade fast-float2 to 0.2.2 or later.

## Is GHSA-jqcp-xc3v-f446 being exploited?

There is no known exploitation of GHSA-jqcp-xc3v-f446 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-jqcp-xc3v-f446 and fix it if it is affected.

What it is: GHSA-jqcp-xc3v-f446 is a memory corruption vulnerability in fast-float2, published on 13 Jan 2025. 
Exploitation: There is no known exploitation of GHSA-jqcp-xc3v-f446 in the wild and no public exploit code.

Affected packages and fixed versions:
- fast-float2 (crates.io): affected all versions; fixed in 0.2.2
- fast-float2 (crates.io): affected all versions; fixed in 0.2.2
- fast-float2 (crates.io): affected from 0.0.0-0; fixed in 0.2.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-jqcp-xc3v-f446/ (Markdown: https://insights.sbomify.com/GHSA-jqcp-xc3v-f446/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-jqcp-xc3v-f446

---
From sbomify Insights: https://insights.sbomify.com/GHSA-jqcp-xc3v-f446/
Summaries are generated and may contain mistakes; the official description above is the record.