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.
opcua(28 total, 6 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix-files | ^0.6 | 0.6.6 | up to date |
| actix-web | ^4.4 | 4.11.0 | up to date |
| base64 | ^0.21 | 0.22.1 | out of date |
| bitflags | ^2.4 | 2.9.1 | up to date |
| byteorder | ^1.4 | 1.5.0 | up to date |
| bytes | ^1.3 | 1.10.1 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.41 | maybe insecure |
| derivative | ^2.2 | 2.2.0 | up to date |
| env_logger | ^0.10 | 0.11.8 | out of date |
| foreign-types | ^0.3 | 0.5.0 | out of date |
| futures | ^0.3 | 0.3.31 | up to date |
| gethostname | ^0.4 | 1.0.2 | out of date |
| lazy_static | ^1.4.0 | 1.5.0 | up to date |
| libc | ^0.2 | 0.2.174 | up to date |
| log | ^0.4 | 0.4.27 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.73 | maybe insecure |
| openssl-sys | ^0.9 | 0.9.109 | up to date |
| parking_lot | ^0.12 | 0.12.4 | up to date |
| regex | ^1.7 | 1.11.1 | up to date |
| rumqttc | ^0.23 | 0.24.0 | out of date |
| serde | ^1.0 | 1.0.219 | up to date |
| serde_derive | ^1.0 | 1.0.219 | up to date |
| serde_json | ^1.0 | 1.0.140 | up to date |
| serde_yaml | ^0.9 | 0.9.34+deprecated | up to date |
| tokio ⚠️ | ^1 | 1.45.1 | maybe insecure |
| tokio-util | ^0.7 | 0.7.15 | up to date |
| url | ^1.6 | 2.5.4 | out of date |
| uuid | ^1.2 | 1.17.0 | up to date |
(2 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| serde_json | ^1.0 | 1.0.140 | up to date |
| tempdir | ^0.3 | 0.3.7 | 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);
openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.
In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).
The maintainers thank quitbug for reporting this vulnerability to us.