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.
tokio-postgres(18 total, 5 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-trait | ^0.1 | 0.1.89 | up to date |
| byteorder | ^1.0 | 1.5.0 | up to date |
| bytes ⚠️ | ^1.0 | 1.11.1 | maybe insecure |
| fallible-iterator | ^0.2 | 0.3.0 | out of date |
| futures-channel | ^0.3 | 0.3.31 | up to date |
| futures-util | ^0.3 | 0.3.31 | up to date |
| log | ^0.4 | 0.4.29 | up to date |
| parking_lot | ^0.12 | 0.12.5 | up to date |
| percent-encoding | ^2.0 | 2.3.2 | up to date |
| phf | ^0.11 | 0.13.1 | out of date |
| pin-project-lite | ^0.2 | 0.2.16 | up to date |
| postgres-protocol | ^0.6.8 | 0.6.10 | up to date |
| postgres-types | ^0.2.9 | 0.2.12 | up to date |
| rand | ^0.9.0 | 0.10.0 | out of date |
| socket2 | ^0.5 | 0.6.2 | out of date |
| tokio | ^1.27 | 1.49.0 | up to date |
| tokio-util | ^0.7 | 0.7.18 | up to date |
| whoami ⚠️ | ^1.4.1 | 2.1.0 | out of date |
(14 total, 4 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| bit-vec | ^0.6 | 0.8.0 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.43 | maybe insecure |
| criterion | ^0.5 | 0.8.2 | out of date |
| env_logger | ^0.11 | 0.11.8 | up to date |
| eui48 | ^1.0 | 1.1.0 | up to date |
| futures-executor | ^0.3 | 0.3.31 | up to date |
| geo-types | ^0.7 | 0.7.18 | up to date |
| jiff | ^0.1 | 0.2.19 | out of date |
| serde | ^1.0 | 1.0.228 | up to date |
| serde_json | ^1.0 | 1.0.149 | up to date |
| smol_str | ^0.1 | 0.3.5 | out of date |
| time | ^0.3 | 0.3.47 | up to date |
| tokio ⚠️ | ^1.0 | 1.49.0 | maybe insecure |
| uuid | ^1.0 | 1.20.0 | up to date |
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.
tokio: reject_remote_clients Configuration corruptionOn Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.
This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.
The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.
Ensure that pipe_mode is set first after initializing a ServerOptions. For example:
let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);
whoami: Stack buffer overflow with whoami on several Unix platformsWith versions of the whoami crate >= 0.5.3 and < 1.5.0, calling any of these functions leads to an immediate stack buffer overflow on illumos and Solaris:
whoami::usernamewhoami::realnamewhoami::username_oswhoami::realname_osWith versions of the whoami crate >= 0.5.3 and < 1.0.1, calling any of the above functions also leads to a stack buffer overflow on these platforms:
This occurs because of an incorrect definition of the passwd struct on those platforms.
As a result of this issue, denial of service and data corruption have both been observed in the wild. The issue is possibly exploitable as well.
This vulnerability also affects other Unix platforms that aren't Linux or macOS.
This issue has been addressed in whoami 1.5.0.
For more information, see this GitHub issue.
bytes: Integer overflow in `BytesMut::reserve`In the unique reclaim path of BytesMut::reserve, the condition
if v_capacity >= new_cap + offset
uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB.
This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.
use bytes::*;
fn main() {
let mut a = BytesMut::from(&b"hello world"[..]);
let mut b = a.split_off(5);
// Ensure b becomes the unique owner of the backing storage
drop(a);
// Trigger overflow in new_cap + offset inside reserve
b.reserve(usize::MAX - 6);
// This call relies on the corrupted cap and may cause UB & HBO
b.put_u8(b'h');
}
Users of BytesMut::reserve are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.