{"answers":{"affected":"1 open source package ship an affected version, including proc-macro-error.","exploited":"There is no known exploitation of RUSTSEC-2024-0370 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2024-0370 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2024-0370 is a vulnerability in proc-macro-error, published on 1 Sep 2024."},"fix_prompt":"Check this codebase for RUSTSEC-2024-0370 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2024-0370 is a vulnerability in proc-macro-error, published on 1 Sep 2024. \nExploitation: There is no known exploitation of RUSTSEC-2024-0370 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- proc-macro-error (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-0370/ (Markdown: https://insights.sbomify.com/RUSTSEC-2024-0370/index.md)","id":"RUSTSEC-2024-0370","markdown":"https://insights.sbomify.com/RUSTSEC-2024-0370/index.md","name":"RUSTSEC-2024-0370","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"workaround","impacts":["other"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust proc-macro library","requires_auth":"none","summary":"The proc-macro-error library is unmaintained, posing supply chain risks and dependency conflicts; developers should migrate to alternatives.","user_interaction":"not_required","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":"proc-macro-error's maintainer seems to be unreachable, with no commits for 2 years, no releases pushed for 4 years, and no activity on the GitLab repo or response to email.\n\nproc-macro-error also depends on `syn 1.x`, which may be bringing duplicate dependencies into dependant build trees.\n\n## Possible Alternative(s)\n\n- [manyhow](https://crates.io/crates/manyhow)\n- [proc-macro2-diagnostics](https://github.com/SergioBenitez/proc-macro2-diagnostics)","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":"proc-macro-error is unmaintained","id":"RUSTSEC-2024-0370","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":"proc-macro-error","purl":"pkg:cargo/proc-macro-error","source":"RUSTSEC-2024-0370"}],"products":null,"published":"2024-09-01","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 proc-macro-error library is unmaintained, posing supply chain risks and dependency conflicts; developers should migrate to alternatives.","url":"https://insights.sbomify.com/RUSTSEC-2024-0370/"}