{"answers":{"affected":"1 open source package ship an affected version, including rutie.","exploited":"There is no known exploitation of RUSTSEC-2024-0448 in the wild and no public exploit code.","fix":"Upgrade rutie to a fixed version for your release line: 0.10.3, 0.11.3, 0.12.1 or 0.13.1.","what":"RUSTSEC-2024-0448 is a memory corruption vulnerability in rutie, published on 25 Nov 2024."},"fix_prompt":"Check this codebase for RUSTSEC-2024-0448 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2024-0448 is a memory corruption vulnerability in rutie, published on 25 Nov 2024. \nExploitation: There is no known exploitation of RUSTSEC-2024-0448 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rutie (crates.io): affected from 0.0.0-0; fixed in 0.10.3, 0.11.3, 0.12.1, 0.13.1, 0.14.1\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/RUSTSEC-2024-0448/ (Markdown: https://insights.sbomify.com/RUSTSEC-2024-0448/index.md)","id":"RUSTSEC-2024-0448","markdown":"https://insights.sbomify.com/RUSTSEC-2024-0448/index.md","name":"RUSTSEC-2024-0448","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust Ruby binding","requires_auth":"none","summary":"A Rust library function unsafely converts a caller-supplied pointer to a slice, allowing null dereference or out-of-bounds reads that can cause crashes or memory corruption.","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":"`parse_arguments` is safe. It takes `arguments: *const AnyObject` and `argc`, and calls `slice::from_raw_parts(arguments, argc as usize)`.\n\nIt does not check that `arguments` is non-null and aligned, or that `argc` elements are initialized. Safe Rust can pass a null pointer or a length past the allocation. The maintainer confirmed this on 2026-10-03, including a debug abort on Rust 1.78+ when Ruby calls an arity -1 method (`to_s` via `format`, `puts`, or `Array#join`) with a NULL `argv` and `argc` of 0.","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":"`parse_arguments` reads a caller-supplied pointer as a slice","id":"RUSTSEC-2024-0448","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.10.3","0.11.3","0.12.1","0.13.1","0.14.1"],"introduced":["0.0.0-0","0.11.0","0.12.0","0.13.0","0.14.0"],"last_affected":[],"package":"rutie","purl":"pkg:cargo/rutie","source":"RUSTSEC-2024-0448"}],"products":null,"published":"2024-11-25","related":[],"sources":[{"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":"A Rust library function unsafely converts a caller-supplied pointer to a slice, allowing null dereference or out-of-bounds reads that can cause crashes or memory corruption.","url":"https://insights.sbomify.com/RUSTSEC-2024-0448/"}