This project contains known security vulnerabilities. Find detailed information at the bottom.
mail-core(14 total, 3 outdated, 1 insecure, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| checked_command | ^0.2.2 | 0.2.4 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| failure | ^0.1.2 | 0.1.8 | up to date |
| futures | ^0.1.24 | 0.3.30 | out of date |
| futures-cpupool | ^0.1.5 | 0.1.8 | up to date |
| lazy_static | ^1.2.0 | 1.4.0 | up to date |
| log | ^0.3.8 | 0.4.21 | out of date |
| mail-headers | ^0.6.0 | 0.6.6 | up to date |
| mail-internals ⚠️ | ^0.2.0 | 0.2.3 | insecure |
| media-type | ^0.4.0-unstable | 0.0.1 | up to date |
| rand | ^0.3.15 | 0.8.5 | out of date |
| serde | ^1.0 | 1.0.198 | up to date |
| soft-ascii-string | ^1.0 | 1.1.0 | up to date |
| vec1 | ^1 | 1.12.0 | up to date |
(2 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| serde_json | ^1.0 | 1.0.116 | up to date |
| serde_test | ^1.0.80 | 1.0.176 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
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.