This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.
futures-util(13 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| futures-channel | ^0.3.4 | 0.3.30 | up to date |
| futures-core | ^0.3.4 | 0.3.30 | up to date |
| futures-io | ^0.3.4 | 0.3.30 | up to date |
| futures-macro | ^0.3.4 | 0.3.30 | up to date |
| futures-sink | ^0.3.4 | 0.3.30 | up to date |
| futures-task ⚠️ | ^0.3.4 | 0.3.30 | maybe insecure |
| futures | ^0.1.25 | 0.3.30 | out of date |
| memchr | ^2.2 | 2.7.2 | up to date |
| pin-utils | ^0.1.0-alpha.4 | 0.1.0 | up to date |
| proc-macro-hack | ^0.5.9 | 0.5.20+deprecated | up to date |
| proc-macro-nested | ^0.1.2 | 0.1.7 | up to date |
| slab | ^0.4 | 0.4.9 | up to date |
| tokio-io | ^0.1.9 | 0.1.13 | up to date |
futures-task: futures_task::waker may cause a use-after-free if used on a type that isn't 'staticAffected versions of the crate did not properly implement a 'static lifetime bound on the waker function.
This resulted in a use-after-free if Waker::wake() is called after original data had been dropped.
The flaw was corrected by adding 'static lifetime bound to the data waker takes.