{"answers":{"affected":"1 open source package ship an affected version, including atty.","exploited":"There is no known exploitation of RUSTSEC-2024-0375 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2024-0375 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2024-0375 is a vulnerability in atty, published on 25 Sep 2024."},"fix_prompt":"Check this codebase for RUSTSEC-2024-0375 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2024-0375 is a vulnerability in atty, published on 25 Sep 2024. \nExploitation: There is no known exploitation of RUSTSEC-2024-0375 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- atty (crates.io): affected from 0.0.0-0; no fix listed\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-0375/ (Markdown: https://insights.sbomify.com/RUSTSEC-2024-0375/index.md)","id":"RUSTSEC-2024-0375","markdown":"https://insights.sbomify.com/RUSTSEC-2024-0375/index.md","name":"RUSTSEC-2024-0375","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust crate","requires_auth":"unknown","summary":"The atty crate is unmaintained, requiring users to migrate to std::io::IsTerminal or is-terminal to ensure continued support and security.","user_interaction":"unknown","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The maintainer of `atty` has [published](https://github.com/softprops/atty/commit/5bfdbe9e48c6ca6a4909e8d5b04f5e843a257e93) an official notice that the crate is no longer\nunder development, and that users should instead rely on the functionality in the standard library's [`IsTerminal`](https://doc.rust-lang.org/std/io/trait.IsTerminal.html) trait.\n\n## Alternative(s)\n\n- [std::io::IsTerminal](https://doc.rust-lang.org/stable/std/io/trait.IsTerminal.html) - Stable since Rust 1.70.0 and the recommended replacement per the `atty` maintainer.\n- [is-terminal](https://crates.io/crates/is-terminal) - Standalone crate supporting Rust older than 1.70.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":false,"headline":"`atty` is unmaintained","id":"RUSTSEC-2024-0375","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"supply_chain","year":"2024"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"atty","purl":"pkg:cargo/atty","source":"RUSTSEC-2024-0375"}],"products":null,"published":"2024-09-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":"The atty crate is unmaintained, requiring users to migrate to std::io::IsTerminal or is-terminal to ensure continued support and security.","url":"https://insights.sbomify.com/RUSTSEC-2024-0375/"}