Skip to content

← Public intelligence

crates.io package

vec-const

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. Unratedcrates.ioPublished

    vec-const attempts to construct a Vec from a pointer to a const slice

    GHSA-jmwx-r3gq-qq3p

    Affected
    • crates.io vec-const < 2.0.0
    Fixed in
    2.0.0· Vendor fix available
    Issue
    Affected versions of this crate claimed to construct a const Vec with nonzero length and capacity, but that cannot be done because such a Vec requires a pointer from an allocator. The implementation was later changed to just construct a std::borrow::Cow.

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

    Out-of-bounds Write in vec-const

    CVE-2021-45680 · GHSA-x76r-966h-5qv9

    Affected
    • crates.io vec-const < 2.0.0
    Fixed in
    2.0.0· Vendor fix available
    Issue
    An issue was discovered in the vec-const crate before 2.0.0 for Rust. It tries to construct a Vec from a pointer to a const slice, leading to memory corruption.

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