{"answers":{"affected":"1 open source package ship an affected version, including serial.","exploited":"There is no known exploitation of RUSTSEC-2017-0008 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2017-0008 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2017-0008 is a vulnerability in serial, published on 2 Jul 2017."},"fix_prompt":"Check this codebase for RUSTSEC-2017-0008 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2017-0008 is a vulnerability in serial, published on 2 Jul 2017. \nExploitation: There is no known exploitation of RUSTSEC-2017-0008 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- serial (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-2017-0008/ (Markdown: https://insights.sbomify.com/RUSTSEC-2017-0008/index.md)","id":"RUSTSEC-2017-0008","markdown":"https://insights.sbomify.com/RUSTSEC-2017-0008/index.md","name":"RUSTSEC-2017-0008","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust serial library","requires_auth":"unknown","summary":"The serial crate is unmaintained, posing supply chain risks; developers should migrate to maintained alternatives like serial2 or tokio-serial.","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 [`serial`](https://crates.io/crates/serial) crate is no longer maintained.\n\nLast release was on 2017-07-02.\n\n## Possible alternatives\n\nConsider using an alternative, for instance the blocking librarys:\n\n- [serial2](https://crates.io/crates/serial2)\n- [serialport](https://crates.io/crates/serialport)\n\nor async alternatives:\n\n- [mio-serial](https://crates.io/crates/mio-serial)\n- [tokio-serial](https://crates.io/crates/tokio-serial)","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":"`serial` crate is unmaintained","id":"RUSTSEC-2017-0008","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"supply_chain","year":"2017"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"serial","purl":"pkg:cargo/serial","source":"RUSTSEC-2017-0008"}],"products":null,"published":"2017-07-02","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 serial crate is unmaintained, posing supply chain risks; developers should migrate to maintained alternatives like serial2 or tokio-serial.","url":"https://insights.sbomify.com/RUSTSEC-2017-0008/"}