RUSTSEC-2020-0138 (CVE-2020-36458)

Vulnerability from osv_rustsec – Published: 2020-11-10 12:00 – Updated: 2023-06-13 13:10 – Source website
VLAI
Summary
ReaderResult should be bounded by Sync
Details

Affected versions of this crate implements Sync for ReaderResult<T, E> with the trait bound T: Send, E: Send.

Since matching on the public enum ReaderResult<T, E> provides access to &T & &E, allowing data race to a non-Sync type T or E. This can result in a memory corruption when multiple threads concurrently access &T or &E.

Suggested fix for the bug is change the trait bounds imposed on T & E to be T: Sync, E: Sync.


{
  "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": "lexer",
        "purl": "pkg:cargo/lexer"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.0-0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": []
    }
  ],
  "aliases": [
    "CVE-2020-36458",
    "GHSA-f997-8gxg-r354"
  ],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "Affected versions of this crate implements `Sync` for `ReaderResult\u003cT, E\u003e` with the trait bound `T: Send, E: Send`.\n\nSince matching on the public enum `ReaderResult\u003cT, E\u003e` provides access to `\u0026T` \u0026 `\u0026E`,\nallowing data race to a non-Sync type `T` or `E`.\nThis can result in a memory corruption when multiple threads concurrently access `\u0026T` or `\u0026E`.\n\nSuggested fix for the bug is change the trait bounds imposed on `T` \u0026 `E` to be `T: Sync, E: Sync`.",
  "id": "RUSTSEC-2020-0138",
  "modified": "2023-06-13T13:10:24Z",
  "published": "2020-11-10T12:00:00Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://crates.io/crates/lexer"
    },
    {
      "type": "ADVISORY",
      "url": "https://rustsec.org/advisories/RUSTSEC-2020-0138.html"
    },
    {
      "type": "REPORT",
      "url": "https://gitlab.com/nathanfaucett/rs-lexer/-/issues/2"
    }
  ],
  "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": "ReaderResult should be bounded by Sync"
}



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…