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.

Crate tokio-native-tls

Dependencies

(2 total, 1 possibly insecure)

CrateRequiredLatestStatus
 native-tls^0.20.2.10up to date
 tokio ⚠️^1.01.18.2maybe insecure

Dev dependencies

(11 total, 4 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 cfg-if^0.11.0.0out of date
 env_logger^0.60.9.0out of date
 futures^0.3.00.3.21up to date
 lazy_static^1.4.01.4.0up to date
 tempfile^3.13.3.0up to date
 tokio ⚠️^1.01.18.2maybe insecure
 tokio-util^0.6.00.7.1out of date
 openssl ⚠️^0.100.10.40maybe insecure
 security-framework^0.22.6.1out of date
 schannel^0.10.1.19up to date
 winapi^0.30.3.9up to date

Security Vulnerabilities

openssl: Use after free in CMS Signing

RUSTSEC-2018-0010

Affected versions of the OpenSSL crate used structures after they'd been freed.

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.