{"answers":{"affected":"2 open source packages ship an affected version, including num-bigint.","exploited":"There is no known exploitation of GHSA-v935-pqmr-g8v9 in the wild and no public exploit code.","fix":"Upgrade num-bigint to 0.4.3 or later.","what":"GHSA-v935-pqmr-g8v9 is a denial of service vulnerability in num-bigint, published on 3 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-v935-pqmr-g8v9 and fix it if it is affected.\n\nWhat it is: GHSA-v935-pqmr-g8v9 is a denial of service vulnerability in num-bigint, published on 3 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-v935-pqmr-g8v9 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- num-bigint (crates.io): affected from 0.4.1; fixed in 0.4.3\n- num-bigint (crates.io): affected from 0.4.1; fixed in 0.4.3\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/GHSA-v935-pqmr-g8v9/ (Markdown: https://insights.sbomify.com/GHSA-v935-pqmr-g8v9/index.md)","id":"GHSA-v935-pqmr-g8v9","markdown":"https://insights.sbomify.com/GHSA-v935-pqmr-g8v9/index.md","name":"GHSA-v935-pqmr-g8v9","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust big integer library","requires_auth":"none","summary":"Unexpected panics in num-bigint multiplication can cause denial of service in applications using the library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\nTwo scenarios were reported where `BigInt` and `BigUint` multiplication may unexpectedly panic.\n\n- The internal `mac3` function did not expect the possibility of non-empty all-zero inputs, leading to an `unwrap()` panic.\n- A buffer was allocated with less capacity than needed for an intermediate result, leading to an assertion panic.\n\nRust panics can either cause stack unwinding or program abort, depending on the application configuration. In some settings, an unexpected panic may constitute a denial-of-service vulnerability.\n\n### Patches\nBoth problems were introduced in version 0.4.1, and are fixed in version 0.4.3.\n\n### For more information\nIf you have any questions or comments about this advisory, please open an issue in the [num-bigint](https://github.com/rust-num/num-bigint) repo.\n\n### Acknowledgements\nThanks to Guido Vranken and Arvid Norberg for privately reporting these issues to the author.\n\n### References\n* [GHSA-v935-pqmr-g8v9](https://github.com/rust-num/num-bigint/security/advisories/GHSA-v935-pqmr-g8v9)\n* [num-bigint#228](https://github.com/rust-num/num-bigint/pull/228)","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":"Unexpected panics in num-bigint","id":"GHSA-v935-pqmr-g8v9","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2021"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.4.3"],"introduced":["0.4.1"],"last_affected":[],"package":"num-bigint","purl":null,"source":"GHSA-v935-pqmr-g8v9"},{"ecosystem":"crates.io","fixed":["0.4.3"],"introduced":["0.4.1"],"last_affected":[],"package":"num-bigint","purl":"pkg:cargo/num-bigint","source":"GHSA-v935-pqmr-g8v9"}],"products":null,"published":"2021-11-03","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Unexpected panics in num-bigint multiplication can cause denial of service in applications using the library.","url":"https://insights.sbomify.com/GHSA-v935-pqmr-g8v9/"}