DynFuture Drop Can Construct a Dangling Reference
Priority LOW 38CWE-843Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub.
Summary
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.
Why it matters now
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | dyn-future (crates.io) | up to 3.0.4 | — | No fix listed | GHSA-j3w3-p6mr-3hrh |
- dyn-future (crates.io) Vendor— Affected up to 3.0.4 Fixed in — No fix listed GHSA-j3w3-p6mr-3hrh
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-j3w3-p6mr-3hrh
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences