rustsec-2020-0130
Vulnerability from osv_rustsec
Published
2020-11-12 12:00
Modified
2023-06-13 13:10
Summary
Bunch<T> unconditionally implements Send/Sync
Details

Affected versions of this crate unconditionally implements Send/Sync for Bunch<T>. This allows users to insert T: !Sync to Bunch<T>. It is possible to create a data race to a T: !Sync by invoking the Bunch::get() API (which returns &T) from multiple threads. It is also possible to send T: !Send to other threads by inserting T inside Bunch<T> and sending Bunch<T> to another thread, allowing to create a data race by inserting types like T = Rc<_>.

Such data races can lead to memory corruption.


{
  "affected": [
    {
      "database_specific": {
        "categories": [
          "memory-corruption",
          "thread-safety"
        ],
        "cvss": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
        "informational": null
      },
      "ecosystem_specific": {
        "affected_functions": null,
        "affects": {
          "arch": [],
          "functions": [],
          "os": []
        }
      },
      "package": {
        "ecosystem": "crates.io",
        "name": "bunch",
        "purl": "pkg:cargo/bunch"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.0-0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": []
    }
  ],
  "aliases": [
    "CVE-2020-36450",
    "GHSA-jwph-qp5h-f9wj"
  ],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "Affected versions of this crate unconditionally implements `Send`/`Sync` for `Bunch\u003cT\u003e`.\nThis allows users to insert `T: !Sync` to `Bunch\u003cT\u003e`. It is possible to create a data race to a `T: !Sync` by invoking the `Bunch::get()` API (which returns `\u0026T`) from multiple threads. It is also possible to send `T: !Send` to other threads by inserting `T` inside `Bunch\u003cT\u003e` and sending `Bunch\u003cT\u003e` to another thread, allowing to create a data race by inserting types like `T = Rc\u003c_\u003e`.\n\nSuch data races can lead to memory corruption.",
  "id": "RUSTSEC-2020-0130",
  "modified": "2023-06-13T13:10:24Z",
  "published": "2020-11-12T12:00:00Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://crates.io/crates/bunch"
    },
    {
      "type": "ADVISORY",
      "url": "https://rustsec.org/advisories/RUSTSEC-2020-0130.html"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/krl/bunch/issues/1"
    }
  ],
  "related": [],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Bunch\u003cT\u003e unconditionally implements Send/Sync"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…