This project contains known security vulnerabilities. Find detailed information at the bottom.
mail-smtp(6 total, 2 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| failure | ^0.1.5 | 0.1.8 | up to date |
| futures | ^0.1 | 0.3.31 | out of date |
| mail-core | ^0.6.2 | 0.6.2 | up to date |
| mail-headers | ^0.6.6 | 0.6.6 | up to date |
| mail-internals ⚠️ | ^0.2.3 | 0.2.3 | insecure |
| new-tokio-smtp | ^0.8.1 | 0.9.1 | out of date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| mail-core | ^0.6.0 | 0.6.2 | up to date |
mail-internals: Use-after-free in `vec_insert_bytes`Incorrect reallocation logic in the function vec_insert_bytes causes a use-after-free.
This function does not have to be called directly to trigger the vulnerability because many methods on EncodingWriter call this function internally.
The mail-* suite is unmaintained and the upstream sources have been actively vandalised.
A fixed mail-internals-ng (and mail-headers-ng and mail-core-ng) crate has been published which fixes this, and a dependency on another unsound crate.