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 orientdb-client

Dependencies

(11 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 chrono ⚠️^0.4.70.4.22maybe insecure
 byteorder^1.3.21.4.3up to date
 r2d2^0.8.50.8.10up to date
 nom^6.17.1.1out of date
 thiserror^1.0.131.0.37up to date
 async-std^1.91.12.0up to date
 async-trait^0.1.100.1.57up to date
 futures^0.30.3.24up to date
 mobc^0.70.7.3up to date
 tokio ⚠️^11.21.2maybe insecure
 uuid^0.81.1.2out of date

Dev dependencies

(2 total, 2 outdated)

CrateRequiredLatestStatus
 dotenv^0.14.10.15.0out of date
 uuid^0.81.1.2out of date

Crate orientdb-macro

Dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 proc-macro2^1.0.91.0.46up to date
 syn^1.0.161.0.101up to date
 quote^1.0.21.0.21up to 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.