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 mysql

Dependencies

(15 total, 4 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 bufstream~0.10.1.4up to date
 io-enum^0.2.11.1.3out of date
 libc^0.20.2.153up to date
 lru ⚠️^0.4.30.12.3out of date
 mysql_common^0.20.10.32.1out of date
 named_pipe~0.40.4.1up to date
 native-tls^0.2.30.2.11up to date
 net2~0.20.2.39up to date
 nix ⚠️^0.17.00.28.0out of date
 percent-encoding^2.1.02.3.1up to date
 serde^11.0.197up to date
 serde_json^11.0.115up to date
 twox-hash^11.6.3up to date
 url^2.12.5.0up to date
 winapi~0.30.3.9up to date

Dev dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 lazy_static^1.4.01.4.0up to date
 rand^0.7.20.8.5out of date
 serde_derive^11.0.197up to date

Security Vulnerabilities

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.

lru: Use after free in lru crate

RUSTSEC-2021-0130

Lru crate has use after free vulnerability.

Lru crate has two functions for getting an iterator. Both iterators give references to key and value. Calling specific functions, like pop(), will remove and free the value, and but it's still possible to access the reference of value which is already dropped causing use after free.