Skip to content

Queue<T> should have a Send bound on its Send/Sync traits

Moderate severity GitHub Reviewed Published Aug 25, 2021 to the GitHub Advisory Database • Updated Jan 9, 2023
Withdrawn This advisory was withdrawn on Aug 24, 2021

Package

cargo scottqueue (Rust)

Affected versions

<= 0.1.0

Patched versions

None

Description

Affected versions of this crate unconditionally implements Send/Sync for Queue<T>.

This allows (1) creating data races to a T: !Sync and (2) sending T: !Send to other threads, resulting in memory corruption or other undefined behavior.

References

Reviewed Aug 6, 2021
Withdrawn Aug 24, 2021
Published to the GitHub Advisory Database Aug 25, 2021
Last updated Jan 9, 2023

Severity

Moderate

EPSS score

Weaknesses

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-v42f-j8fx-99f3

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.