RUSTSEC-2020-0060 (CVE-2020-35906)

Vulnerability from osv_rustsec – Published: 2020-09-04 12:00 – Updated: 2023-06-13 13:10 – Source website
VLAI
Summary
futures_task::waker may cause a use-after-free if used on a type that isn't 'static
Details

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.


{
  "affected": [
    {
      "database_specific": {
        "categories": [
          "code-execution",
          "memory-corruption"
        ],
        "cvss": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
        "informational": null
      },
      "ecosystem_specific": {
        "affected_functions": null,
        "affects": {
          "arch": [],
          "functions": [
            "futures_task::waker"
          ],
          "os": []
        }
      },
      "package": {
        "ecosystem": "crates.io",
        "name": "futures-task",
        "purl": "pkg:cargo/futures-task"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.2.2-0"
            },
            {
              "fixed": "0.3.6"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": []
    }
  ],
  "aliases": [
    "CVE-2020-35906",
    "GHSA-r93v-9p5q-vhpf"
  ],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "Affected versions of the crate did not properly implement a `\u0027static` lifetime bound on the `waker` function.\nThis resulted in a use-after-free if `Waker::wake()` is called after original data had been dropped.\n\nThe flaw was corrected by adding `\u0027static` lifetime bound to the data `waker` takes.",
  "id": "RUSTSEC-2020-0060",
  "modified": "2023-06-13T13:10:24Z",
  "published": "2020-09-04T12:00:00Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://crates.io/crates/futures-task"
    },
    {
      "type": "ADVISORY",
      "url": "https://rustsec.org/advisories/RUSTSEC-2020-0060.html"
    },
    {
      "type": "WEB",
      "url": "https://github.com/rust-lang/futures-rs/pull/2206"
    }
  ],
  "related": [],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "futures_task::waker may cause a use-after-free if used on a type that isn\u0027t \u0027static"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…