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.
libcontainer(23 total, 5 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| caps | ^0.5.6 | 0.5.6 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.44 | maybe insecure |
| fastrand | ^2.3.0 | 2.4.1 | up to date |
| libc | ^0.2.180 | 0.2.186 | up to date |
| libcgroups | ^0.6.0 | 0.6.0 | up to date |
| libseccomp | ^0.4.0 | 0.4.0 | up to date |
| nc | ^0.9.7 | 0.9.7 | up to date |
| netlink-packet-core | ^0.8.1 | 0.8.1 | up to date |
| netlink-packet-route | ^0.26.0 | 0.30.0 | out of date |
| netlink-sys | ^0.8.8 | 0.8.8 | up to date |
| nix | ^0.29.0 | 0.31.2 | out of date |
| oci-spec | ^0.9.0 | 0.9.0 | up to date |
| pathrs | ^0.2.3 | 0.2.4 | up to date |
| prctl | ^1.0.0 | 1.0.0 | up to date |
| procfs | ^0.17.0 | 0.18.0 | out of date |
| protobuf ⚠️ | =3.2.0 | 3.7.2 | out of date |
| regex | ^1.12.3 | 1.12.3 | up to date |
| rust-criu | ^0.4.0 | 0.5.0 | out of date |
| safe-path | ^0.1.0 | 0.1.0 | up to date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.149 | up to date |
| thiserror | ^2.0.18 | 2.0.18 | up to date |
| tracing | ^0.1.44 | 0.1.44 | up to date |
(7 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1.0 | 1.0.102 | up to date |
| oci-spec | ~0.9.0 | 0.9.0 | up to date |
| quickcheck | ^1 | 1.1.0 | up to date |
| rand | ^0.10.0 | 0.10.1 | up to date |
| scopeguard | ^1 | 1.2.0 | up to date |
| serial_test | ^3.4.0 | 3.4.0 | up to date |
| tempfile | ^3 | 3.27.0 | 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.
protobuf: Crash due to uncontrolled recursion in protobuf crateAffected version of this crate did not properly parse unknown fields when parsing a user-supplied input.
This allows an attacker to cause a stack overflow when parsing the mssage on untrusted data.