futures-intrusive
Activity
- Latest release
- 3y ago
- Total releases
- 11
- Cadence
- ~2 months
- Last 12 months
- 0
Details
- License
- MIT OR Apache-2.0
- First release
- May 22, 2019
| Version | Released | |
|---|---|---|
0.5.0
unknown
|
0.5.0
unknown
Dependencies (13)
+ 5 more |
|
0.4.2
unknown
|
0.4.2
unknown
Dependencies (13)
+ 5 more |
|
0.4.1
unknown
yanked
|
0.4.1
unknown
yanked
Dependencies (13)
+ 5 more |
|
0.4.0
unknown
|
0.4.0
unknown
Dependencies (13)
+ 5 more |
|
0.3.1
unknown
1 CVE
CVE-2020-35915
GHSA-4hjg-cx88-g9f9
RUSTSEC-2020-0072
Aug 25, 2021
Data races in futures-intrusive
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
GenericMutexGuard was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is. This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code. The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait. Fixed in
0.4.0
References Updated Nov 08, 2023 · Source: OSV.dev |
0.3.1
unknown
Dependencies (13)
+ 5 more |
|
0.3.0
unknown
1 CVE
CVE-2020-35915
GHSA-4hjg-cx88-g9f9
RUSTSEC-2020-0072
Aug 25, 2021
Data races in futures-intrusive
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
GenericMutexGuard was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is. This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code. The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait. Fixed in
0.4.0
References Updated Nov 08, 2023 · Source: OSV.dev |
0.3.0
unknown
Dependencies (13)
+ 5 more |
|
0.2.2
unknown
1 CVE
CVE-2020-35915
GHSA-4hjg-cx88-g9f9
RUSTSEC-2020-0072
Aug 25, 2021
Data races in futures-intrusive
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
GenericMutexGuard was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is. This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code. The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait. Fixed in
0.4.0
References Updated Nov 08, 2023 · Source: OSV.dev |
0.2.2
unknown
Dependencies (12)
+ 4 more |
|
0.2.1
unknown
1 CVE
CVE-2020-35915
GHSA-4hjg-cx88-g9f9
RUSTSEC-2020-0072
Aug 25, 2021
Data races in futures-intrusive
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
GenericMutexGuard was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is. This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code. The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait. Fixed in
0.4.0
References Updated Nov 08, 2023 · Source: OSV.dev |
0.2.1
unknown
Dependencies (11)
+ 3 more |
|
0.2.0
unknown
1 CVE
CVE-2020-35915
GHSA-4hjg-cx88-g9f9
RUSTSEC-2020-0072
Aug 25, 2021
Data races in futures-intrusive
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
GenericMutexGuard was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is. This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code. The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait. Fixed in
0.4.0
References Updated Nov 08, 2023 · Source: OSV.dev |
0.2.0
unknown
Dependencies (10)
+ 2 more |
|
0.1.1
unknown
1 CVE
CVE-2020-35915
GHSA-4hjg-cx88-g9f9
RUSTSEC-2020-0072
Aug 25, 2021
Data races in futures-intrusive
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
GenericMutexGuard was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is. This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code. The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait. Fixed in
0.4.0
References Updated Nov 08, 2023 · Source: OSV.dev |
0.1.1
unknown
Dependencies (9)
+ 1 more |
|
0.1.0
unknown
1 CVE
CVE-2020-35915
GHSA-4hjg-cx88-g9f9
RUSTSEC-2020-0072
Aug 25, 2021
Data races in futures-intrusive
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
GenericMutexGuard was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is. This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code. The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait. Fixed in
0.4.0
References Updated Nov 08, 2023 · Source: OSV.dev |
0.1.0
unknown
Dependencies (9)
+ 1 more |