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 log4rs

Dependencies

(18 total, 9 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 antidote^1.01.0.0up to date
 chrono ⚠️^0.30.4.38out of date
 crossbeam ⚠️^0.2.90.8.4out of date
 flate2^0.21.0.30out of date
 fnv^1.01.0.7up to date
 humantime^1.02.1.0out of date
 kernel32-sys^0.20.2.2up to date
 libc^0.20.2.153up to date
 log^0.30.4.21out of date
 log-mdc^0.10.1.0up to date
 serde^1.01.0.202up to date
 serde-value^0.50.7.0out of date
 serde_derive^1.01.0.202up to date
 serde_json^1.01.0.117up to date
 serde_yaml ⚠️^0.70.9.34+deprecatedout of date
 toml^0.40.8.13out of date
 typemap^0.30.3.3up to date
 winapi^0.20.3.9out of date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 tempdir^0.30.3.7up to date

Security Vulnerabilities

serde_yaml: Uncontrolled recursion leads to abort in deserialization

RUSTSEC-2018-0005

Affected versions of this crate did not properly check for recursion while deserializing aliases.

This allows an attacker to make a YAML file with an alias referring to itself causing an abort.

The flaw was corrected by checking the recursion depth.

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

crossbeam: `MsQueue` `push`/`pop` use the wrong orderings

RUSTSEC-2022-0029