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.
gremlin-client(24 total, 6 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| serde | ^1.0 | 1.0.215 | up to date |
| serde_json | ^1.0 | 1.0.133 | up to date |
| serde_derive | ^1.0 | 1.0.215 | up to date |
| r2d2 | ^0.8.3 | 0.8.10 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| lazy_static | ^1.3.0 | 1.5.0 | up to date |
| base64 | ^0.21.4 | 0.22.1 | out of date |
| native-tls | ^0.2.3 | 0.2.12 | up to date |
| tungstenite | ^0.20.1 | 0.24.0 | out of date |
| async-tungstenite | ^0.23 | 0.28.0 | out of date |
| async-std | ^1.4.0 | 1.13.0 | up to date |
| async-trait | ^0.1.10 | 0.1.83 | up to date |
| async-tls | ^0.12 | 0.13.0 | out of date |
| tokio-native-tls | ^0.3.0 | 0.3.1 | up to date |
| tokio-stream | ^0.1.2 | 0.1.16 | up to date |
| rustls ⚠️ | ^0.20 | 0.23.17 | out of date |
| webpki | ^0.22.2 | 0.22.4 | up to date |
| thiserror | ^1.0.20 | 2.0.3 | out of date |
| mobc | ^0.8 | 0.8.5 | up to date |
| url | ^2.1.0 | 2.5.3 | up to date |
| futures | ^0.3.1 | 0.3.31 | up to date |
| pin-project-lite | ^0.2 | 0.2.15 | up to date |
| tokio ⚠️ | ^1 | 1.41.1 | maybe insecure |
| uuid | ^1.1.2 | 1.11.0 | up to date |
gremlin-tutorialNo external dependencies! 🙌
gremlin-derive(3 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| proc-macro2 | ^1.0.9 | 1.0.89 | up to date |
| syn | ^1.0.16 | 2.0.87 | out of date |
| quote | ^1.0.2 | 1.0.37 | up to date |
gremlin-cli(10 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| rustyline | ^6.2.0 | 15.0.0 | out of date |
| smol | ^0.4.3 | 2.0.2 | out of date |
| shellwords | ^1.1.0 | 1.1.0 | up to date |
| futures | ^0.3.5 | 0.3.31 | up to date |
| async-std | ^1.6.3 | 1.13.0 | up to date |
| uuid | ^0.8.1 | 1.11.0 | out of date |
| chrono ⚠️ | ^0.4.15 | 0.4.38 | maybe insecure |
| structopt | ^0.3 | 0.3.26 | up to date |
| prettytable-rs | ^0.10.0 | 0.10.0 | up to date |
| anyhow | ^1.0.32 | 1.0.93 | 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.
tokio: reject_remote_clients Configuration corruptionOn Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.
This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.
The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.
Ensure that pipe_mode is set first after initializing a ServerOptions. For example:
let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.