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 eventstore

Dependencies

(22 total, 15 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 base64^0.110.22.0out of date
 byteorder^1.21.5.0up to date
 bytes^0.51.6.0out of date
 futures^0.30.3.30up to date
 http^0.21.1.0out of date
 log^0.40.4.21up to date
 prost^0.60.12.3out of date
 prost-derive^0.60.12.3out of date
 prost-types ⚠️^0.60.12.3out of date
 protobuf^2.103.4.0out of date
 rand^0.70.8.5out of date
 reqwest^0.100.12.2out of date
 rustls^0.160.23.4out of date
 serde^1.01.0.197up to date
 serde_derive^1.01.0.197up to date
 serde_json^1.01.0.115up to date
 tokio ⚠️^0.21.36.0out of date
 tokio-byteorder^0.20.3.0out of date
 tonic^0.10.11.0out of date
 uuid^0.81.8.0out of date
 vec1^1.41.12.0up to date
 webpki ⚠️^0.210.22.4out of date

Dev dependencies

(2 total, 2 outdated)

CrateRequiredLatestStatus
 env_logger^0.60.11.3out of date
 tokio-test^0.20.4.4out of date

Security Vulnerabilities

prost-types: Conversion from `prost_types::Timestamp` to `SystemTime` can cause an overflow and panic

RUSTSEC-2021-0073

Affected versions of this crate contained a bug in which untrusted input could cause an overflow and panic when converting a Timestamp to SystemTime.

It is recommended to upgrade to prost-types v0.8 and switch the usage of From<Timestamp> for SystemTime to TryFrom<Timestamp> for SystemTime.

See #438 for more information.

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.

webpki: webpki: CPU denial of service in certificate path building

RUSTSEC-2023-0052

When this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.

Both TLS clients and TLS servers that accept client certificate are affected.

This was previously reported in https://github.com/briansmith/webpki/issues/69 and re-reported recently by Luke Malinowski.

webpki 0.22.1 included a partial fix and webpki 0.22.2 added further fixes.