Data races in v9
Priority LOW 38CWE-362Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
Affected versions of this crate unconditionally implement `Sync` for `SyncRef<T>`. This definition allows data races if `&T` is accessible through `&SyncRef`. `SyncRef<T>` derives `Clone` and `Debug`, and the default implementations of those traits access `&T` by invoking `T::clone()` & `T::fmt()`. It is possible to create data races & undefined behavior by concurrently invoking `SyncRef<T>::clone()` or `SyncRef<T>::fmt()` from multiple threads with `T: !Sync`.
Why it matters now
Fix Fixed v9 (crates.io): 0.1.43
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | v9 (crates.io) | before 0.1.43 | 0.1.43 | Patch available | GHSA-pfjq-935c-4895 |
- v9 (crates.io) Vendor— Affected before 0.1.43 Fixed in 0.1.43 Patch available GHSA-pfjq-935c-4895
Remediation
- Fix · GHSA-pfjq-935c-4895 v9 (crates.io) Fixed in 0.1.43 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-pfjq-935c-4895
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences