Lucene search
K

2673 matches found

Github Security Blog
Github Security Blog
added 2021/08/25 9:0 p.m.20 views

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

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

5AI score
Exploits0References3Affected Software1
OSV
OSV
added 2021/08/25 9:0 p.m.0 views

GHSA-8892-84WF-CG8F SyncChannel<T> can move 'T: !Send' to other threads

Affected versions of this crate unconditionally implement Send/Sync for SyncChannel. SyncChannel doesn't provide access to &T but merely serves as a channel that consumes and returns owned T. Users can create UB in safe Rust by sending T: !Send to other threads with SyncChannel::send/recv APIs...

8.1CVSS5.9AI score0.00766EPSS
Exploits0References3
Github Security Blog
Github Security Blog
added 2021/08/25 9:0 p.m.14 views

SyncChannel<T> can move 'T: !Send' to other threads

Affected versions of this crate unconditionally implement Send/Sync for SyncChannel. SyncChannel doesn't provide access to &T but merely serves as a channel that consumes and returns owned T. Users can create UB in safe Rust by sending T: !Send to other threads with SyncChannel::send/recv APIs...

6.8AI score
Exploits0References3Affected Software1
Github Security Blog
Github Security Blog
added 2021/08/25 9:0 p.m.16 views

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

Affected versions of this crate unconditionally implements Send/Sync for Queue. 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...

3.8AI score
Exploits0References3Affected Software1
Github Security Blog
Github Security Blog
added 2021/08/25 9:0 p.m.16 views

Singleton lacks bounds on Send and Sync.

Singleton is meant to be a static object that can be initialized lazily. In order to satisfy the requirement that static items must implement Sync, Singleton implemented both Sync and Send unconditionally. This allows for a bug where non-Sync types such as Cell can be used in singletons and cause...

1.4AI score
Exploits0References3Affected Software1
OSV
OSV
added 2021/08/25 9:0 p.m.2 views

GHSA-JH2G-XHQQ-X4W9 Send/Sync bound needed on T for Send/Sync impl of RcuCell<T>

Affected versions of this crate unconditionally implement Send/Sync for RcuCell. This allows users to send T: !Send to other threads while T enclosed within RcuCell, and allows users to concurrently access T: !Sync by using the APIs of RcuCell that provide access to &T. This can result in memory...

7.3AI score
Exploits0References4
OSV
OSV
added 2021/08/25 9:0 p.m.1 views

GHSA-XWXC-J97J-84GF Race condition in Parc

In the affected versions of this crate, LockWeak unconditionally implemented Send with no trait bounds on T. LockWeak doesn't own T and only provides &T. This allows concurrent access to a non-Sync T, which can cause undefined behavior like data races...

8.1CVSS7.1AI score0.00833EPSS
Exploits1References3
Github Security Blog
Github Security Blog
added 2021/08/25 9:0 p.m.9 views

Race condition in Parc

In the affected versions of this crate, LockWeak unconditionally implemented Send with no trait bounds on T. LockWeak doesn't own T and only provides &T. This allows concurrent access to a non-Sync T, which can cause undefined behavior like data races...

6.8AI score
Exploits0References3Affected Software1
Github Security Blog
Github Security Blog
added 2021/08/25 8:59 p.m.12 views

MvccRwLock allows data races & aliasing violations

Affected versions of the noisesearch crate unconditionally implement Send/Sync for MvccRwLock. This can lead to data races when types that are either !Send or !Sync e.g. Rc, Arc are contained inside MvccRwLock and sent across thread boundaries. The data races can potentially lead to memory...

3AI score
Exploits0References3Affected Software1
OSV
OSV
added 2021/08/25 8:59 p.m.1 views

GHSA-JF43-3V8J-QWWR Data races in multiqueue

Affected versions of multiqueue unconditionally implemented Send for types used in queue implementations InnerSend, InnerRecv, FutInnerSend, FutInnerRecv. This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior...

8.1CVSS5.9AI score0.01098EPSS
Exploits1References3
Github Security Blog
Github Security Blog
added 2021/08/25 8:59 p.m.14 views

Data races in multiqueue

Affected versions of multiqueue unconditionally implemented Send for types used in queue implementations InnerSend, InnerRecv, FutInnerSend, FutInnerRecv. This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior...

6.8AI score
Exploits0References3Affected Software1
OSV
OSV
added 2021/08/25 8:59 p.m.1 views

GHSA-JWPH-QP5H-F9WJ Data races in bunch

An issue was discovered in the bunch crate through 2020-11-12 for Rust. Affected versions of this crate unconditionally implements Send/Sync for Bunch. This allows users to insert T: !Sync to Bunch. It is possible to create a data race to a T: !Sync by invoking the Bunch::get API which returns &T...

8.1CVSS7.1AI score0.01249EPSS
Exploits1References5
Github Security Blog
Github Security Blog
added 2021/08/25 8:59 p.m.38 views

Data races in bunch

An issue was discovered in the bunch crate through 2020-11-12 for Rust. Affected versions of this crate unconditionally implements Send/Sync for Bunch. This allows users to insert T: !Sync to Bunch. It is possible to create a data race to a T: !Sync by invoking the Bunch::get API which returns &T...

8.1CVSS7.7AI score0.01249EPSS
Exploits1References5Affected Software1
Github Security Blog
Github Security Blog
added 2021/08/25 8:59 p.m.22 views

Data races in convec

Affected versions of this crate unconditionally implement Send/Sync for ConVec. This allows users to insert T that is not Send or not Sync. This allows users to create data races by using non-Send types like Arc or Rc as T in ConVec. It is also possible to create data races by using types like Ce...

8.1CVSS7.7AI score0.00766EPSS
Exploits0References4Affected Software1
OSV
OSV
added 2021/08/25 8:59 p.m.3 views

GHSA-36CG-4JFF-5863 Data races in signal-simple

Affected versions of this crate unconditionally implement Send/Sync for SyncChannel. SyncChannel doesn't provide access to &T but merely serves as a channel that consumes and returns owned T. Users can create UB in safe Rust by sending T: !Send to other threads with SyncChannel::send/recv APIs...

8.1CVSS5.9AI score0.00766EPSS
Exploits0References5
Github Security Blog
Github Security Blog
added 2021/08/25 8:59 p.m.29 views

Data races in signal-simple

Affected versions of this crate unconditionally implement Send/Sync for SyncChannel. SyncChannel doesn't provide access to &T but merely serves as a channel that consumes and returns owned T. Users can create UB in safe Rust by sending T: !Send to other threads with SyncChannel::send/recv APIs...

8.1CVSS7.7AI score0.00766EPSS
Exploits0References5Affected Software1
Github Security Blog
Github Security Blog
added 2021/08/25 8:59 p.m.30 views

Data races in libsbc

Affected versions of this crate implements Send for Decoder for any R: Read. This allows Decoder to contain R: !Send and carry move it to another thread. This can result in undefined behavior such as memory corruption from data race on R, or dropping R = MutexGuard from a thread that didn't lock...

8.1CVSS7.9AI score0.00766EPSS
Exploits0References5Affected Software1
Github Security Blog
Github Security Blog
added 2021/08/25 8:58 p.m.35 views

Data races in ticketed_lock

Affected versions of this crate unconditionally implemented Send for ReadTicket & WriteTicket. 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/WriteTicket. Such data...

8.1CVSS7.9AI score0.00766EPSS
Exploits0References6Affected Software1
OSV
OSV
added 2021/08/25 8:58 p.m.19 views

GHSA-FG42-VWXX-XX5J Data race in tiny_future

tinyfuture contains a light-weight implementation of Futures. The Future type it has lacked bound on its Send and Sync traits. This allows for a bug where non-thread safe types such as Cell can be used in Futures and cause data races in concurrent programs. The flaw was corrected in commit c79191...

8.1CVSS7.8AI score0.00766EPSS
Exploits0References6
OSV
OSV
added 2021/08/25 8:58 p.m.13 views

GHSA-368F-29C3-4F2R Data race in conqueue

Affected versions of this crate unconditionally implemented Send/Sync for QueueSender, allowing to send non-Send T to other threads by invoking &QueueSender.send. This fails to prevent users from creating data races by sending types like Rc or Arc to other threads, which can lead to memory...

8.1CVSS7.9AI score0.00847EPSS
Exploits0References5
Rows per page
Query Builder