Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Withdrawn — this advisory has been retracted
🦀
🦀 crates.io
Not in CISA KEV
HIGH severity

GHSA-gq4h-f254-7cw9

HIGHFix: kvark/ticketed_lock@a986a93

GHSA-gq4h-f254-7cw9 is a high-severity (CVSS 8.1) CWE-362 vulnerability in ticketed_lock. O3 Security confirms whether GHSA-gq4h-f254-7cw9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Duplicate Advisory: Data races in ticketed_lock

Also known asCVE-2020-36439GHSA-77m6-x95j-75r5RUSTSEC-2020-0119
Published
Aug 25, 2021
Updated
Feb 3, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Feb 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🦀ticketed_lock

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

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-77m6-x95j-75r5. This link is maintained to preserve external references.

Original Description

Affected versions of this crate unconditionally implemented Send for ReadTicket<T> & WriteTicket<T>. This allows to send non-Send T to other threads.

This can allows creating data races by cloning types with internal mutability and sending them to other threads (as T of ReadTicket<T>/WriteTicket<T>). Such data races can cause memory corruption or other undefined behavior.

The flaw was corrected in commit a986a93 by adding T: Send bounds to Send impls of ReadTicket<T>/WriteTicket<T>.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.ioticketed_lockall versions0.3.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ticketed_lock. 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.

  2. Fix

    Update ticketed_lock to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gq4h-f254-7cw9 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-gq4h-f254-7cw9 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-gq4h-f254-7cw9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-77m6-x95j-75r5. This link is maintained to preserve external references. ## Original Description Affected versions of this crate unconditionally implemented `Send` for `ReadTicket<T>` & `WriteTicket<T>`. This allows to send non-Send `T` to other threads. This can allows creating data races by cloning types with internal mutability and sending them to other threads (as `T` of `ReadTicket<T>`/`WriteTicket<T>`). Such data races can cause memory corruption or other undefined behavior. The flaw was corrected
O3 Security · Impact-Aware SCA

Is GHSA-gq4h-f254-7cw9 in your dependencies?

O3 detects GHSA-gq4h-f254-7cw9 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.

GHSA-gq4h-f254-7cw9: Duplicate Advisory:… | O3 Security