Skip to content

← Public intelligence

crates.io package

rocket

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. High, CVSS 7.3crates.ioPublished

    Use after free in Rocket

    CVE-2021-29935 · GHSA-vcw4-8ph6-7vw8

    Affected
    • crates.io rocket < 0.4.7
    Fixed in
    0.4.7· Vendor fix available
    Issue
    Affected versions of this crate transmuted a &str to a &'static str before pushing it into a StackVec, this value was then popped later in the same function. This was assumed to be safe because the reference would be valid while the method's stack was active. In between the push and the pop, however, a function f was called that could invoke a user provided function. If the user provided panicked, then the assumption used by the function was no longer true and the transmute to &'static would create an illegal static reference to the string. This could result in a freed string being used during (such as in a Drop implementation) or after (e.g through catchunwind) the panic unwinding. This flaw was corrected in commit e325e2f by using a guard object to ensure that the &'static str was dropped inside the function.

    Recommended action: Upgrade to 0.4.7 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 8.1crates.ioPublished

    Data races in rocket

    CVE-2020-35882 · GHSA-8q2v-67v7-6vc6

    Affected
    • crates.io rocket >= 0.4.0, < 0.4.5
    Fixed in
    0.4.5· Vendor fix available
    Issue
    The affected version of rocket contains a Clone trait implementation of LocalRequest that reuses the pointer to inner Request object. This causes data race in rare combinations of APIs if the original and the cloned objects are modified at the same time.

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