Skip to content

← Public intelligence

crates.io package

nanorand

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

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

  1. Unratedcrates.ioPublished

    Aliased mutable references from tls_rand & TlsWyRand

    GHSA-p6gj-gpc8-f8xw

    Affected
    • crates.io nanorand >= 0.5.0, < 0.6.1
    Fixed in
    0.6.1· Vendor fix available
    Issue
    TlsWyRand's implementation of Deref unconditionally dereferences a raw pointer, and returns multiple mutable references to the same object, which is undefined behavior.

    Recommended action: Upgrade to 0.6.1 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 →
  2. Critical, CVSS 9.8crates.ioPublished

    Pointer dereference in nanorand

    CVE-2021-45705 · GHSA-r57r-j98g-587f

    Affected
    • crates.io nanorand >= 0.5.0, < 0.6.1
    Fixed in
    0.6.1· Vendor fix available
    Issue
    An issue was discovered in the nanorand crate before 0.6.1 for Rust. There can be multiple mutable references to the same object because the TlsWyRand Deref implementation dereferences a raw pointer.

    Recommended action: Upgrade to 0.6.1 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 →
  3. Medium, CVSS 5.1crates.ioPublished

    Improper random number generation in nanorand

    CVE-2020-35926 · GHSA-m9m5-cg5h-r582

    Affected
    • crates.io nanorand < 0.5.1
    Fixed in
    0.5.1· Vendor fix available
    Issue
    In versions of nanorand prior to 0.5.1, RandomGen implementations for standard unsigned integers could fail to properly generate numbers, due to using bit-shifting to truncate a 64-bit number, rather than just an as conversion. This often manifested as RNGs returning nothing but 0, including the cryptographically secure ChaCha random number generator.

    Recommended action: Upgrade to 0.5.1 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 →