Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

num-bigint

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Unratedcrates.ioPublished

    Unexpected panics in num-bigint

    GHSA-v935-pqmr-g8v9

    Affected
    • crates.io num-bigint >= 0.4.1, < 0.4.3
    Fixed in
    0.4.3· Vendor fix available
    Issue
    Impact Two scenarios were reported where BigInt and BigUint multiplication may unexpectedly panic. - The internal mac3 function did not expect the possibility of non-empty all-zero inputs, leading to an unwrap() panic. - A buffer was allocated with less capacity than needed for an intermediate result, leading to an assertion panic. Rust 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. Patches Both problems were introduced in version 0.4.1, and are fixed in version 0.4.3. For more information If you have any questions or comments about this advisory, please open an issue in the num-bigint repo. Acknowledgements Thanks to Guido Vranken and Arvid Norberg for privately reporting these issues to the author. References GHSA-v935-pqmr-g8v9 num-bigint#228

    Recommended action: Upgrade to 0.4.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →