{"answers":{"affected":"1 open source package ship an affected version, including stainless_ffmpeg.","exploited":"There is no known exploitation of RUSTSEC-2025-0169 in the wild and no public exploit code.","fix":"Upgrade stainless_ffmpeg to 0.6.0 or later.","what":"RUSTSEC-2025-0169 is a memory corruption vulnerability in stainless_ffmpeg, published on 24 Apr 2025."},"fix_prompt":"Check this codebase for RUSTSEC-2025-0169 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2025-0169 is a memory corruption vulnerability in stainless_ffmpeg, published on 24 Apr 2025. \nExploitation: There is no known exploitation of RUSTSEC-2025-0169 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- stainless_ffmpeg (crates.io): affected from 0.0.0-0; fixed in 0.6.0\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-2025-0169/ (Markdown: https://insights.sbomify.com/RUSTSEC-2025-0169/index.md)","id":"RUSTSEC-2025-0169","markdown":"https://insights.sbomify.com/RUSTSEC-2025-0169/index.md","name":"RUSTSEC-2025-0169","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust FFmpeg bindings","requires_auth":"none","summary":"Safe Rust code can trigger undefined behavior via out-of-bounds pointer access in stainless_ffmpeg stream accessors, potentially leading to crashes or code execution.","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":"Affected versions of `stainless_ffmpeg` exposed several safe public methods on `FormatContext` that accepted a `stream_index` parameter and used it in unsafe pointer operations without checking whether the index was valid. These methods performed pointer arithmetic and dereferenced the resulting stream pointer. Safe callers could pass a negative or out-of-bounds `stream_index`, which could cause out-of-bounds pointer access and undefined behavior from safe Rust code.\n\nThe issue was fixed in version `0.6.0` by marking the affected stream accessor methods as `unsafe` and documenting that callers must ensure `stream_index` is a valid stream index.","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":"`FormatContext` stream accessors can cause undefined behavior from safe code","id":"RUSTSEC-2025-0169","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.6.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"stainless_ffmpeg","purl":"pkg:cargo/stainless_ffmpeg","source":"RUSTSEC-2025-0169"}],"products":null,"published":"2025-04-24","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":"Safe Rust code can trigger undefined behavior via out-of-bounds pointer access in stainless_ffmpeg stream accessors, potentially leading to crashes or code execution.","url":"https://insights.sbomify.com/RUSTSEC-2025-0169/"}