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-postgres

Dependencies

(12 total, 10 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bytes^0.41.10.1out of date
 fallible-iterator^0.20.3.0out of date
 futures-preview=0.3.0-alpha.190.2.2up to date
 log^0.40.4.27up to date
 parking_lot^0.90.12.4out of date
 percent-encoding^1.02.3.1out of date
 phf^0.7.230.12.1out of date
 pin-project^0.41.1.10out of date
 pin-utils=0.1.0-alpha.40.1.0out of date
 postgres-protocol=0.5.0-alpha.10.6.8out of date
 postgres-types=0.1.0-alpha.10.2.9out of date
 tokio ⚠️=0.2.0-alpha.61.46.0out of date

Dev dependencies

(9 total, 6 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bit-vec^0.60.8.0out of date
 chrono ⚠️^0.40.4.41maybe insecure
 env_logger^0.50.11.8out of date
 eui48^0.41.1.0out of date
 geo-types^0.40.7.16out of date
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 tokio ⚠️=0.2.0-alpha.61.46.0out of date
 uuid^0.71.17.0out of date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References

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.