GHSA-2QV5-7MW5-J3CG

Vulnerability from github – Published: 2023-04-03 22:53 – Updated: 2023-04-03 22:53
VLAI?
Summary
spin-rs initialisation failure in `Once::try_call_once` can lead to undefined behaviour for other initialisers
Details

Once::try_call_once is unsound if invoked more than once concurrently and any call fails to initialise successfully.

Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "crates.io",
        "name": "spin"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.9.3"
            },
            {
              "fixed": "0.9.8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": true,
    "github_reviewed_at": "2023-04-03T22:53:18Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "`Once::try_call_once` is unsound if invoked more than once concurrently and any call fails to initialise successfully.\n",
  "id": "GHSA-2qv5-7mw5-j3cg",
  "modified": "2023-04-03T22:53:18Z",
  "published": "2023-04-03T22:53:18Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/mvdnes/spin-rs/issues/148"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/mvdnes/spin-rs"
    },
    {
      "type": "WEB",
      "url": "https://rustsec.org/advisories/RUSTSEC-2023-0031.html"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "spin-rs initialisation failure in `Once::try_call_once` can lead to undefined behaviour for other initialisers"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

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.



Detection rules are retrieved from Rulezet.