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.

Crate libcontainer

Dependencies

(20 total, 4 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 caps^0.5.50.5.5up to date
 chrono ⚠️^0.40.4.42maybe insecure
 fastrand^2.3.02.3.0up to date
 libc^0.2.1750.2.175up to date
 libcgroups^0.5.50.5.5up to date
 libseccomp^0.3.00.4.0out of date
 nc^0.9.60.9.6up to date
 nix^0.29.00.30.1out of date
 oci-spec^0.8.20.8.2up to date
 once_cell^1.21.31.21.3up to date
 prctl^1.0.01.0.0up to date
 procfs^0.17.00.18.0out of date
 protobuf ⚠️=3.2.03.7.2out of date
 regex^1.10.61.11.2up to date
 rust-criu^0.4.00.4.0up to date
 safe-path^0.1.00.1.0up to date
 serde^1.01.0.219up to date
 serde_json^1.01.0.143up to date
 thiserror^2.0.142.0.16up to date
 tracing^0.1.410.1.41up to date

Dev dependencies

(7 total, all up-to-date)

CrateRequiredLatestStatus
 anyhow^1.01.0.99up to date
 oci-spec~0.8.20.8.2up to date
 quickcheck^11.0.3up to date
 rand^0.9.20.9.2up to date
 scopeguard^11.2.0up to date
 serial_test^3.1.13.2.0up to date
 tempfile^33.22.0up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-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.

Workarounds

No workarounds are known.

References

protobuf: Crash due to uncontrolled recursion in protobuf crate

RUSTSEC-2024-0437

Affected 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.