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.
sim2h(44 total, 26 outdated, 4 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| backtrace | =0.3.27 | 0.3.71 | out of date |
| base64 | =0.10.1 | 0.22.0 | out of date |
| chashmap | =2.2.2 | 2.2.2 | up to date |
| chrono ⚠️ | =0.4.6 | 0.4.38 | out of date |
| crossbeam-channel | =0.3.8 | 0.5.12 | out of date |
| env_logger | =0.6.1 | 0.11.3 | out of date |
| futures | =0.3.2 | 0.3.30 | out of date |
| hcid | =0.0.6 | 0.0.6 | up to date |
| holochain_common | =0.0.46-alpha1 | N/A | up to date |
| holochain_core_types | =0.0.46-alpha1 | 0.0.34 | up to date |
| holochain_json_api | =0.0.23 | 0.0.50 | out of date |
| holochain_locksmith | =0.0.46-alpha1 | N/A | up to date |
| holochain_metrics | =0.0.46-alpha1 | 0.2.7 | out of date |
| holochain_persistence_api | =0.0.18 | 0.0.18 | up to date |
| holochain_tracing | =0.0.24 | 0.0.24 | up to date |
| holochain_tracing_macros | =0.0.24 | 0.0.24 | up to date |
| im | =14.0.0 | 15.1.0 | out of date |
| in_stream | =0.0.46-alpha1 | N/A | up to date |
| lazy_static | =1.4.0 | 1.4.0 | up to date |
| lib3h | =0.0.42 | 0.0.42 | up to date |
| lib3h_crypto_api | =0.0.42 | 0.0.42 | up to date |
| lib3h_protocol | =0.0.42 | 0.0.42 | up to date |
| lib3h_sodium | =0.0.42 | 0.0.42 | up to date |
| lib3h_zombie_actor | =0.0.42 | 0.0.42 | up to date |
| nanoid | =0.2.0 | 0.4.0 | out of date |
| native-tls | =0.2.3 | 0.2.11 | out of date |
| newrelic | =0.2.2 | 0.2.2 | up to date |
| num_cpus | =1.11.1 | 1.16.0 | out of date |
| openssl ⚠️ | =0.10.25 | 0.10.64 | out of date |
| parking_lot | =0.8.0 | 0.12.1 | out of date |
| rand | =0.7.3 | 0.8.5 | out of date |
| serde | =1.0.104 | 1.0.198 | out of date |
| serde_derive | =1.0.104 | 1.0.198 | out of date |
| serde_json | =1.0.47 | 1.0.116 | out of date |
| snowflake | =1.3.0 | 1.3.0 | up to date |
| threadpool | =1.7.1 | 1.8.1 | out of date |
| tokio ⚠️ | =0.2.11 | 1.37.0 | out of date |
| tracing | =0.1.13 | 0.1.40 | out of date |
| tracing-futures | =0.2.2 | 0.2.5 | out of date |
| tungstenite ⚠️ | =0.9.2 | 0.21.0 | out of date |
| twox-hash | ^1.5.0 | 1.6.3 | up to date |
| url | =2.1.0 | 2.5.0 | out of date |
| url2 | =0.0.4 | 0.0.6 | out of date |
| uuid | ^0.4 | 1.8.0 | out of 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: Data race when sending and receiving after closing a `oneshot` channelIf 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.
openssl: `openssl` `X509NameBuilder::build` returned object is not thread safeOpenSSL has a modified bit that it can set on on X509_NAME objects. If this
bit is set then the object is not thread-safe even when it appears the code is
not modifying the value.
Thanks to David Benjamin (Google) for reporting this issue.
openssl: `openssl` `SubjectAlternativeName` and `ExtendedKeyUsage::other` allow arbitrary file readSubjectAlternativeName and ExtendedKeyUsage arguments were parsed using the OpenSSL
function X509V3_EXT_nconf. This function parses all input using an OpenSSL mini-language
which can perform arbitrary file reads.
Thanks to David Benjamin (Google) for reporting this issue.
openssl: `openssl` `X509Extension::new` and `X509Extension::new_nid` null pointer dereferenceThese functions would crash when the context argument was None with certain extension types.
Thanks to David Benjamin (Google) for reporting this issue.
openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-readWhen this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.
tungstenite: Tungstenite allows remote attackers to cause a denial of serviceThe Tungstenite crate through 0.20.0 for Rust allows remote attackers to cause a denial of service (minutes of CPU consumption) via an excessive length of an HTTP header in a client handshake. The length affects both how many times a parse is attempted (e.g., thousands of times) and the average amount of data for each parse attempt (e.g., millions of bytes).