Total
1661 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2020-36438 | 1 Tiny Future Project | 1 Tiny Future | 2024-08-04 | 8.1 High |
| An issue was discovered in the tiny_future crate before 0.4.0 for Rust. Future<T> does not have bounds on its Send and Sync traits. | ||||
| CVE-2020-36558 | 2 Linux, Redhat | 5 Linux Kernel, Enterprise Linux, Rhel Eus and 2 more | 2024-08-04 | 5.1 Medium |
| A race condition in the Linux kernel before 5.5.7 involving VT_RESIZEX could lead to a NULL pointer dereference and general protection fault. | ||||
| CVE-2020-36436 | 1 Unicycle Project | 1 Unicycle | 2024-08-04 | 8.1 High |
| An issue was discovered in the unicycle crate before 0.7.1 for Rust. PinSlab<T> and Unordered<T, S> do not have bounds on their Send and Sync traits. | ||||
| CVE-2020-36446 | 1 Signal-simple Project | 1 Signal-simple | 2024-08-04 | 8.1 High |
| An issue was discovered in the signal-simple crate through 2020-11-15 for Rust. There are unconditional implementations of Send and Sync for SyncChannel<T>. | ||||
| CVE-2020-36440 | 1 Libsbc Project | 1 Libsbc | 2024-08-04 | 8.1 High |
| An issue was discovered in the libsbc crate before 0.1.5 for Rust. For Decoder<R>, it implements Send for any R: Read. | ||||
| CVE-2020-36444 | 1 Async-coap Project | 1 Async-coap | 2024-08-04 | 8.1 High |
| An issue was discovered in the async-coap crate through 2020-12-08 for Rust. Send and Sync are implemented for ArcGuard<RC, T> without trait bounds on RC. | ||||
| CVE-2020-36445 | 1 Project | 1 Convec | 2024-08-04 | 8.1 High |
| An issue was discovered in the convec crate through 2020-11-24 for Rust. There are unconditional implementations of Send and Sync for ConVec<T>. | ||||
| CVE-2020-36435 | 1 Ruspiro-singleton Project | 1 Ruspiro-singleton | 2024-08-04 | 8.1 High |
| An issue was discovered in the ruspiro-singleton crate before 0.4.1 for Rust. In Singleton, Send and Sync do not have bounds checks. | ||||
| CVE-2020-36458 | 1 Lexer Project | 1 Lexer | 2024-08-04 | 8.1 High |
| An issue was discovered in the lexer crate through 2020-11-10 for Rust. For ReaderResult<T, E>, there is an implementation of Sync with a trait bound of T: Send, E: Send. | ||||
| CVE-2020-36437 | 1 Conqueue Project | 1 Conqueue | 2024-08-04 | 8.1 High |
| An issue was discovered in the conqueue crate before 0.4.0 for Rust. There are unconditional implementations of Send and Sync for QueueSender<T>. | ||||
| CVE-2020-36439 | 1 Ticketed Lock Project | 1 Ticketed Lock | 2024-08-04 | 8.1 High |
| An issue was discovered in the ticketed_lock crate before 0.3.0 for Rust. There are unconditional implementations of Send for ReadTicket<T> and WriteTicket<T>. | ||||
| CVE-2020-36203 | 1 Reffers Project | 1 Reffers | 2024-08-04 | 4.7 Medium |
| An issue was discovered in the reffers crate through 2020-12-01 for Rust. ARefss can contain a !Send,!Sync object, leading to a data race and memory corruption. | ||||
| CVE-2020-35874 | 1 Internment Project | 1 Internment | 2024-08-04 | 8.1 High |
| An issue was discovered in the internment crate through 2020-05-28 for Rust. ArcIntern::drop has a race condition and resultant use-after-free. | ||||
| CVE-2020-35928 | 1 Concread Project | 1 Concread | 2024-08-04 | 4.7 Medium |
| An issue was discovered in the concread crate before 0.2.6 for Rust. Attackers can cause an ARCache<K,V> data race by sending types that do not implement Send/Sync. | ||||
| CVE-2020-35914 | 1 Lock Api Project | 1 Lock Api | 2024-08-04 | 4.7 Medium |
| An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockWriteGuard unsoundness. | ||||
| CVE-2020-35912 | 1 Lock Api Project | 1 Lock Api | 2024-08-04 | 4.7 Medium |
| An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockWriteGuard unsoundness. | ||||
| CVE-2020-35905 | 1 Rust-lang | 1 Future-utils | 2024-08-04 | 4.7 Medium |
| An issue was discovered in the futures-util crate before 0.3.7 for Rust. MutexGuard::map can cause a data race for certain closure situations (in safe code). | ||||
| CVE-2020-35913 | 1 Lock Api Project | 1 Lock Api | 2024-08-04 | 4.7 Medium |
| An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness. | ||||
| CVE-2020-35911 | 1 Lock Api Project | 1 Lock Api | 2024-08-04 | 4.7 Medium |
| An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of MappedRwLockReadGuard unsoundness. | ||||
| CVE-2020-35882 | 1 Rocket | 1 Rocket | 2024-08-04 | 8.1 High |
| An issue was discovered in the rocket crate before 0.4.5 for Rust. LocalRequest::clone creates more than one mutable references to the same object, possibly causing a data race. | ||||