{"answers":{"affected":"3 open source packages ship an affected version, including fast-float2.","exploited":"There is no known exploitation of GHSA-jqcp-xc3v-f446 in the wild and no public exploit code.","fix":"Upgrade fast-float2 to 0.2.2 or later.","what":"GHSA-jqcp-xc3v-f446 is a memory corruption vulnerability in fast-float2, published on 13 Jan 2025."},"fix_prompt":"Check this codebase for GHSA-jqcp-xc3v-f446 and fix it if it is affected.\n\nWhat it is: GHSA-jqcp-xc3v-f446 is a memory corruption vulnerability in fast-float2, published on 13 Jan 2025. \nExploitation: There is no known exploitation of GHSA-jqcp-xc3v-f446 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- fast-float2 (crates.io): affected all versions; fixed in 0.2.2\n- fast-float2 (crates.io): affected all versions; fixed in 0.2.2\n- fast-float2 (crates.io): affected from 0.0.0-0; fixed in 0.2.2\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-jqcp-xc3v-f446/ (Markdown: https://insights.sbomify.com/GHSA-jqcp-xc3v-f446/index.md)","id":"GHSA-jqcp-xc3v-f446","markdown":"https://insights.sbomify.com/GHSA-jqcp-xc3v-f446/index.md","name":"GHSA-jqcp-xc3v-f446","record":{"aliases":["RUSTSEC-2025-0002"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust parsing library","requires_auth":"none","summary":"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.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In this case, the \"fast_float2::common::AsciiStr::first\" method within the \"AsciiStr\" struct \nuses the unsafe keyword to reading from memory without performing bounds checking. \nSpecifically, it directly dereferences a pointer offset by \"self.ptr\".\nBecause of the above reason, the method accesses invalid memory address when it takes an empty string as its input.\nThis approach violates Rust’s memory safety guarantees, as it can lead to invalid memory access if empty buffer is provided.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"fast-float2 has a segmentation fault due to lack of bound check","id":"GHSA-jqcp-xc3v-f446","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.2.2"],"introduced":["0"],"last_affected":[],"package":"fast-float2","purl":null,"source":"GHSA-jqcp-xc3v-f446"},{"ecosystem":"crates.io","fixed":["0.2.2"],"introduced":["0"],"last_affected":[],"package":"fast-float2","purl":"pkg:cargo/fast-float2","source":"GHSA-jqcp-xc3v-f446"},{"ecosystem":"crates.io","fixed":["0.2.2"],"introduced":["0.0.0-0"],"last_affected":[],"package":"fast-float2","purl":"pkg:cargo/fast-float2","source":"RUSTSEC-2025-0002"}],"products":null,"published":"2025-01-13","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"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.","url":"https://insights.sbomify.com/GHSA-jqcp-xc3v-f446/"}