Advisory Database
  • Advisories
  • Dependency Scanning
  1. cargo
  2. ›
  3. slock
  4. ›
  5. CVE-2020-36455

CVE-2020-36455: Data races in slock

August 25, 2021

An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock unconditionally implements Send and Sync.

References

  • github.com/BrokenLamp/slock-rs
  • github.com/BrokenLamp/slock-rs/commit/719df35f55b6cab4ca2a7f840347a06ecbd8aac6
  • github.com/BrokenLamp/slock-rs/issues/2
  • github.com/advisories/GHSA-mc36-5m36-hjh5
  • nvd.nist.gov/vuln/detail/CVE-2020-36455
  • raw.githubusercontent.com/rustsec/advisory-db/main/crates/slock/RUSTSEC-2020-0135.md
  • rustsec.org/advisories/RUSTSEC-2020-0135.html

Code Behaviors & Features

Detect and mitigate CVE-2020-36455 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 0.2.0

Fixed versions

  • 0.2.0

Solution

Upgrade to version 0.2.0 or above.

Impact 8.1 HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Learn more about CVSS

Weakness

  • CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
  • CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')

Source file

cargo/slock/CVE-2020-36455.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 14 May 2025 12:15:10 +0000.