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 pueue

Dependencies

(23 total, 12 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.81up to date
 async-std^11.12.0up to date
 byteorder^11.5.0up to date
 bytes^0.51.6.0out of date
 chrono ⚠️^0.40.4.37maybe insecure
 chrono-english^0.1.00.1.7up to date
 comfy-table^0.1.07.1.0out of date
 config^0.100.14.0out of date
 crossterm^0.160.27.0out of date
 dirs^25.0.1out of date
 log^0.40.4.21up to date
 nix ⚠️^0.170.28.0out of date
 rand^0.70.8.5out of date
 serde^1.01.0.197up to date
 serde_derive^1.01.0.197up to date
 serde_json^1.01.0.115up to date
 serde_yaml ⚠️^0.80.9.34+deprecatedout of date
 simplelog^0.70.12.2out of date
 structopt^0.30.3.26up to date
 strum^0.180.26.2out of date
 strum_macros^0.180.26.2out of date
 tempfile^33.10.1up to date
 users^0.90.11.0out of date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 proptest^0.91.4.0out of 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

nix: Out-of-bounds write in nix::unistd::getgrouplist

RUSTSEC-2021-0119

On certain platforms, if a user has more than 16 groups, the nix::unistd::getgrouplist function will call the libc getgrouplist function with a length parameter greater than the size of the buffer it provides, resulting in an out-of-bounds write and memory corruption.

The libc getgrouplist function takes an in/out parameter ngroups specifying the size of the group buffer. When the buffer is too small to hold all of the requested user's group memberships, some libc implementations, including glibc and Solaris libc, will modify ngroups to indicate the actual number of groups for the user, in addition to returning an error. The version of nix::unistd::getgrouplist in nix 0.16.0 and up will resize the buffer to twice its size, but will not read or modify the ngroups variable. Thus, if the user has more than twice as many groups as the initial buffer size of 8, the next call to getgrouplist will then write past the end of the buffer.

The issue would require editing /etc/groups to exploit, which is usually only editable by the root user.