This project contains known security vulnerabilities. Find detailed information at the bottom.
pueue(23 total, 12 outdated, 1 insecure, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1 | 1.0.100 | up to date |
| async-std | ^1 | 1.13.2 | up to date |
| byteorder | ^1 | 1.5.0 | up to date |
| bytes | ^0.5 | 1.10.1 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.42 | maybe insecure |
| chrono-english | ^0.1.0 | 0.1.8 | up to date |
| comfy-table | ^0.1.0 | 7.2.1 | out of date |
| config | ^0.10 | 0.15.18 | out of date |
| crossterm | ^0.16 | 0.29.0 | out of date |
| dirs | ^2 | 6.0.0 | out of date |
| log | ^0.4 | 0.4.28 | up to date |
| nix ⚠️ | ^0.17 | 0.30.1 | out of date |
| rand | ^0.7 | 0.9.2 | out of date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_derive | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.145 | up to date |
| serde_yaml ⚠️ | ^0.8 | 0.9.34+deprecated | out of date |
| simplelog | ^0.7 | 0.12.2 | out of date |
| structopt | ^0.3 | 0.3.26 | up to date |
| strum | ^0.18 | 0.27.2 | out of date |
| strum_macros | ^0.18 | 0.27.2 | out of date |
| tempfile | ^3 | 3.23.0 | up to date |
| users ⚠️ | ^0.9 | 0.11.0 | insecure |
(1 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| proptest | ^0.9 | 1.9.0 | out of date |
serde_yaml: Uncontrolled recursion leads to abort in deserializationAffected 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` 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.
nix: Out-of-bounds write in nix::unistd::getgrouplistOn 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.
users: `root` appended to group listingsAffected versions append root to group listings, unless the correct listing
has exactly 1024 groups.
This affects both:
If the caller uses this information for access control, this may lead to privilege escalation.
This crate is not currently maintained, so a patched version is not available.
Versions older than 0.8.0 do not contain the affected functions, so downgrading to them is a workaround.