Skip to content

← Public intelligence

crates.io package

sized-chunks

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

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

  1. High, CVSS 7.5crates.ioPublished

    Array size is not checked in sized-chunks

    CVE-2020-25792 · GHSA-mp6f-p9gp-vpj9

    Affected
    • crates.io sized-chunks < 0.6.3
    Fixed in
    0.6.3· Vendor fix available
    Issue
    An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with pair().

    Recommended action: Upgrade to 0.6.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 →
  2. High, CVSS 7.5crates.ioPublished

    Unaligned references in sized-chunks

    CVE-2020-25796 · GHSA-fqpx-cq8x-9wp4

    Affected
    • crates.io sized-chunks < 0.6.3
    Fixed in
    0.6.3· Vendor fix available
    Issue
    An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the InlineArray implementation, an unaligned reference may be generated for a type that has a large alignment requirement.

    Recommended action: Upgrade to 0.6.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 →
  3. High, CVSS 7.5crates.ioPublished

    Missing release of memory in sized-chunks

    CVE-2020-25794 · GHSA-rfgg-vccr-m46m

    Affected
    • crates.io sized-chunks < 0.6.3
    Fixed in
    0.6.3· Vendor fix available
    Issue
    An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, clone can have a memory-safety issue upon a panic.

    Recommended action: Upgrade to 0.6.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 →
  4. High, CVSS 7.5crates.ioPublished

    Array size is not checked in sized-chunks

    CVE-2020-25791 · GHSA-9p9m-9xww-qjcx

    Affected
    • crates.io sized-chunks < 0.6.3
    Fixed in
    0.6.3· Vendor fix available
    Issue
    An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with unit().

    Recommended action: Upgrade to 0.6.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 →
  5. High, CVSS 7.5crates.ioPublished

    Array size is not checked in sized-chunks

    CVE-2020-25793 · GHSA-64gv-qg2v-vxv6

    Affected
    • crates.io sized-chunks < 0.6.3
    Fixed in
    0.6.3· Vendor fix available
    Issue
    An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with From<InlineArray<A, T.

    Recommended action: Upgrade to 0.6.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 →
  6. High, CVSS 7.5crates.ioPublished

    Missing release of memory in sized-chunks

    CVE-2020-25795 · GHSA-x54v-qxxr-93qc

    Affected
    • crates.io sized-chunks < 0.6.3
    Fixed in
    0.6.3· Vendor fix available
    Issue
    Chunk: Array size is not checked when constructed with unit() and pair(). Array size is not checked when constructed with From<InlineArray<A, T. Clone and insertfrom are not panic-safe; A panicking iterator causes memory safety issues with them. InlineArray: Generates unaligned references for types with a large alignment requirement.

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