Skip to content

← Public intelligence

crates.io package

futures-task

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.8crates.ioPublished

    futures_task::waker may cause a use-after-free if used on a type that isn't 'static

    CVE-2020-35906 · GHSA-r93v-9p5q-vhpf

    Affected
    • crates.io futures-task >= 0.2.1, < 0.3.6
    Fixed in
    0.3.6· Vendor fix available
    Issue
    Affected versions of the crate did not properly implement a 'static lifetime bound on the waker function. This resulted in a use-after-free if Waker::wake() is called after original data had been dropped. The flaw was corrected by adding 'static lifetime bound to the data waker takes.

    Recommended action: Upgrade to 0.3.6 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. Medium, CVSS 5.5crates.ioPublished

    futures_task::noop_waker_ref can segfault due to dereferencing a NULL pointer

    CVE-2020-35907 · GHSA-p9m5-3hj7-cp5r

    Affected
    • crates.io futures-task < 0.3.5
    Fixed in
    0.3.5· Vendor fix available
    Issue
    Affected versions of the crate used a UnsafeCell in thread-local storage to return a noop waker reference, assuming that the reference would never be returned from another thread. This resulted in a segmentation fault crash if Waker::wakebyref() was called on a waker returned from another thread due to it attempting to dereference a pointer that wasn't accessible from the main thread.

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