Lucene search
K

9 matches found

OSV
OSV
added 2026/04/04 5:55 a.m.0 views

GHSA-J3W3-P6MR-3HRH DynFuture Drop Can Construct a Dangling Reference

DynFuture is unsound because its Drop implementation transmutes a trait-object reference into unrelated reference types, which constructs an invalid reference from trait object metadata. This issue was reproduced against dyn-future 3.0.4 under Miri. The crate is unmaintained...

6.3CVSS5.9AI score
Exploits0References3
Github Security Blog
Github Security Blog
added 2026/04/04 5:55 a.m.7 views

DynFuture Drop Can Construct a Dangling Reference

DynFuture is unsound because its Drop implementation transmutes a trait-object reference into unrelated reference types, which constructs an invalid reference from trait object metadata. This issue was reproduced against dyn-future 3.0.4 under Miri. The crate is unmaintained...

5.9AI score
Exploits0References3Affected Software1
OSV
OSV
added 2026/01/21 12:0 p.m.3 views

RUSTSEC-2026-0079 `DynFuture` drop can construct a dangling reference

DynFuture is unsound because its Drop implementation transmutes a trait-object reference into unrelated reference types, which constructs an invalid reference from trait object metadata. This issue was reproduced against dyn-future 3.0.4 under Miri. And the crate is unmaintained...

5.8AI score
Exploits0References3
RustSec
RustSec
added 2026/01/21 12:0 p.m.3 views

`DynFuture` drop can construct a dangling reference

DynFuture is unsound because its Drop implementation transmutes a trait-object reference into unrelated reference types, which constructs an invalid reference from trait object metadata. This issue was reproduced against dyn-future 3.0.4 under Miri. And the crate is unmaintained...

5.8AI score
Exploits0
Github Security Blog
Github Security Blog
added 2023/11/14 6:32 p.m.21 views

Insufficient covariance check makes self_cell unsound

All public versions prior to 1.02 used an insufficient check to ensure that users correctly marked the dependent type as either covariant or notcovariant. This allowed users to mark a dependent as covariant even though its type was not covariant but invariant, for certain invariant types involvin...

7AI score
Exploits0References3Affected Software1
OSV
OSV
added 2023/11/10 12:0 p.m.12 views

RUSTSEC-2023-0070 Insufficient covariance check makes self_cell unsound

All public versions prior to 1.02 used an insufficient check to ensure that users correctly marked the dependent type as either covariant or notcovariant. This allowed users to mark a dependent as covariant even though its type was not covariant but invariant, for certain invariant types involvin...

7.1AI score
Exploits0References3
RustSec
RustSec
added 2023/11/10 12:0 p.m.2 views

Insufficient covariance check makes self_cell unsound

All public versions prior to 1.02 used an insufficient check to ensure that users correctly marked the dependent type as either covariant or notcovariant. This allowed users to mark a dependent as covariant even though its type was not covariant but invariant, for certain invariant types involvin...

7.1AI score
Exploits0Affected Software1
OSV
OSV
added 2022/06/17 12:12 a.m.0 views

GHSA-8MV5-7X95-7WCF `mopa` is technically unsound

The mopa crate redefines the deprecated TraitObject struct from core::raw like so: rust reprC deriveCopy, Clone dochidden pub struct TraitObject pub data: mut , pub vtable: mut , This is done to then transmute a reference to a trait object &dyn Trait for any trait Trait into this struct and...

9.8CVSS6.4AI score0.00931EPSS
Exploits0References3
OSV
OSV
added 2022/01/06 10:11 p.m.2 views

GHSA-2GXJ-QRP2-53JV Incorrect reliance on Trait memory layout in mopa

The mopa crate redefines the deprecated TraitObject struct from core::raw. This is done to then transmute a reference to a trait object &dyn Trait for any trait Trait into this struct and retrieve the data field for the purpose of downcasting. This is used to implement downcastrefunchecked, in...

9.8CVSS7.7AI score0.00931EPSS
Exploits0References5
Rows per page
Query Builder