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.
zeromq(21 total, 1 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-dispatcher | ^0.1 | 0.1.2 | up to date |
| async-std | ^1 | 1.13.0 | up to date |
| async-trait | ^0.1 | 0.1.83 | up to date |
| asynchronous-codec | ^0.7 | 0.7.0 | up to date |
| bytes | ^1 | 1.8.0 | up to date |
| crossbeam-queue | ^0.3 | 0.3.11 | up to date |
| dashmap | ^5 | 6.1.0 | out of date |
| futures-channel | ^0.3 | 0.3.31 | up to date |
| futures-io | ^0.3 | 0.3.31 | up to date |
| futures-task ⚠️ | ^0.3 | 0.3.31 | maybe insecure |
| futures-util | ^0.3 | 0.3.31 | up to date |
| log | ^0.4 | 0.4.22 | up to date |
| num-traits | ^0.2 | 0.2.19 | up to date |
| once_cell | ^1 | 1.20.2 | up to date |
| parking_lot | ^0.12 | 0.12.3 | up to date |
| rand | ^0.8 | 0.8.5 | up to date |
| regex ⚠️ | ^1 | 1.11.1 | maybe insecure |
| thiserror | ^1 | 1.0.65 | up to date |
| tokio ⚠️ | ^1 | 1.41.0 | maybe insecure |
| tokio-util | ^0.7 | 0.7.12 | up to date |
| uuid | ^1 | 1.11.0 | up to date |
(6 total, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-dispatcher | ^0.1 | 0.1.2 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.38 | maybe insecure |
| criterion | ^0.5 | 0.5.1 | up to date |
| hex | ^0.4 | 0.4.3 | up to date |
| pretty_env_logger | ^0.5 | 0.5.0 | up to date |
| zmq2 | ^0.5 | 0.5.0 | up to date |
futures-task: futures_task::waker may cause a use-after-free if used on a type that isn't 'staticAffected versions of the crate did not properly implement a 'static lifetime bound on the waker function.
This resulted in a use-after-free if Waker::wake() is called after original data had been dropped.
The flaw was corrected by adding 'static lifetime bound to the data waker takes.
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.
regex: Regexes with large repetitions on empty sub-expressions take a very long time to parseThe Rust Security Response WG was notified that the regex crate did not
properly limit the complexity of the regular expressions (regex) it parses. An
attacker could use this security issue to perform a denial of service, by
sending a specially crafted regex to a service accepting untrusted regexes. No
known vulnerability is present when parsing untrusted input with trusted
regexes.
This issue has been assigned CVE-2022-24713. The severity of this vulnerability
is "high" when the regex crate is used to parse untrusted regexes. Other uses
of the regex crate are not affected by this vulnerability.
The regex crate features built-in mitigations to prevent denial of service
attacks caused by untrusted regexes, or untrusted input matched by trusted
regexes. Those (tunable) mitigations already provide sane defaults to prevent
attacks. This guarantee is documented and it's considered part of the crate's
API.
Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.
All versions of the regex crate before or equal to 1.5.4 are affected by this
issue. The fix is include starting from regex 1.5.5.
We recommend everyone accepting user-controlled regexes to upgrade immediately
to the latest version of the regex crate.
Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.
We want to thank Addison Crump for responsibly disclosing this to us according to the Rust security policy, and for helping review the fix.
We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory.
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);