Skip to content

← Public intelligence

crates.io package

lock_api

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

5 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.7crates.ioPublished

    Data races in lock_api

    CVE-2020-35913 · GHSA-hj9h-wrgg-hgmx

    Affected
    • crates.io lock_api < 0.4.2
    Fixed in
    0.4.2· Vendor fix available
    Issue
    An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness.

    Recommended action: Upgrade to 0.4.2 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 4.7crates.ioPublished

    Data races in lock_api

    CVE-2020-35912 · GHSA-5wg8-7c9q-794v

    Affected
    • crates.io lock_api < 0.4.2
    Fixed in
    0.4.2· Vendor fix available
    Issue
    An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness.

    Recommended action: Upgrade to 0.4.2 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 →
  3. Medium, CVSS 4.7crates.ioPublished

    Data races in lock_api

    CVE-2020-35911 · GHSA-vh4p-6j7g-f4j9

    Affected
    • crates.io lock_api < 0.4.2
    Fixed in
    0.4.2· Vendor fix available
    Issue
    An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness.

    Recommended action: Upgrade to 0.4.2 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 →
  4. Medium, CVSS 4.7crates.ioPublished

    Data races in lock_api

    CVE-2020-35914 · GHSA-gmv4-vmx3-x9f3

    Affected
    • crates.io lock_api < 0.4.2
    Fixed in
    0.4.2· Vendor fix available
    Issue
    An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness.

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

    Data races in lock_api

    CVE-2020-35910 · GHSA-ppj3-7jw3-8vc4

    Affected
    • crates.io lock_api < 0.4.2
    Fixed in
    0.4.2· Vendor fix available
    Issue
    An issue was discovered in the lockapi crate before 0.4.2 for Rust. A data race can occur because of MappedMutexGuard unsoundness.

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