Skip to content

← Public intelligence

crates.io package

rand_core

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

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

  1. Critical, CVSS 9.8crates.ioPublished

    Unaligned memory access in rand_core

    CVE-2020-25576 · GHSA-mmc9-pwm7-qj5w

    Affected
    • crates.io rand_core >= 0.4.0, < 0.4.2; < 0.3.1
    Fixed in
    0.3.10.4.2· Vendor fix available
    Issue
    Impact Affected versions of this crate violated alignment when casting byte slices to integer slices, resulting in undefined behavior. randcore::BlockRng::nextu64 and randcore::BlockRng::fillbytes are affected. Patches The flaw was corrected by Ralf Jung and Diggory Hardy for randcore = 0.4.2. Workarounds None. References See Rand's changelog. For more information If you have any questions or comments about this advisory, open an issue in the Rand repository.

    Recommended action: Upgrade to 0.4.2 or 0.3.1 by release line, 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

    Incorrect check on buffer length in rand_core

    CVE-2021-27378 · GHSA-w7j2-35mf-95p7

    Affected
    • crates.io rand_core >= 0.6.0, < 0.6.2
    Fixed in
    0.6.2· Vendor fix available
    Issue
    An issue was discovered in the randcore crate before 0.6.2 for Rust. Because readu32into and readu64into mishandle certain buffer-length checks, a random number generator may be seeded with too little data. The vulnerability was introduced in v0.6.0. The advisory doesn't apply to earlier minor version numbers. Because readu32into and readu64into mishandle certain buffer-length checks, a random number generator may be seeded with too little data.

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