How severe is GHSA-83r8-p8v6-6gfm?

GHSA-83r8-p8v6-6gfm has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-83r8-p8v6-6gfm?

GHSA-83r8-p8v6-6gfm affects the following packages: slock (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-83r8-p8v6-6gfm?

Update slock to 0.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-83r8-p8v6-6gfm is resolved across your whole dependency graph.

How do I detect GHSA-83r8-p8v6-6gfm in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for slock. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-83r8-p8v6-6gfm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-83r8-p8v6-6gfm?

O3 pinpoints whether GHSA-83r8-p8v6-6gfm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-83r8-p8v6-6gfm actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-83r8-p8v6-6gfm, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-83r8-p8v6-6gfm?

GHSA-83r8-p8v6-6gfm has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 67th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-83r8-p8v6-6gfm?

GHSA-83r8-p8v6-6gfm is classified as CWE-77 (CWE-77). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-83r8-p8v6-6gfm published, and has it been updated?

GHSA-83r8-p8v6-6gfm was published on August 25, 2021 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

GHSA-83r8-p8v6-6gfm

HIGH

Slock<T> allows sending non-Send types across thread boundaries

Also known asCVE-2020-36455 GHSA-mc36-5m36-hjh5RUSTSEC-2020-0135

Published

Aug 25, 2021

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk67th percentile+0.80%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🦀slock

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Slock<T> unconditionally implements Send/Sync.

Affected versions of this crate allows sending non-Send types to other threads, which can lead to data races and memory corruption due to the data race.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`slock`	all versions	0.2.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An issue was discovered in the slock crate through 2020-11-17 for Rust. …

rustsec.orgNVDAug 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for slock. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update slock to 0.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-83r8-p8v6-6gfm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-83r8-p8v6-6gfm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-83r8-p8v6-6gfm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`Slock<T>` unconditionally implements `Send`/`Sync`. Affected versions of this crate allows sending non-Send types to other threads, which can lead to data races and memory corruption due to the data race.

O3 Security · Impact-Aware SCA

Is GHSA-83r8-p8v6-6gfm in your dependencies?

O3 detects GHSA-83r8-p8v6-6gfm across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works