Deps.rs

virtual-net 0.7.0

[![dependency status](https://deps.rs/crate/virtual-net/0.7.0/status.svg)](https://deps.rs/crate/virtual-net/0.7.0)

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 virtual-net

Dependencies

(25 total, 10 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.01.0.92up to date
 async-trait^0.10.1.83up to date
 base64^0.210.22.1out of date
 bincode^1.31.3.3up to date
 bytecheck^0.6.80.8.0out of date
 bytes^1.11.8.0up to date
 derivative^22.2.0up to date
 futures-util^0.30.3.31up to date
 hyper^11.5.0up to date
 hyper-tungstenite^0.130.15.0out of date
 hyper-util^0.1.50.1.10up to date
 libc^0.20.2.161up to date
 mio ⚠️^0.81.0.2out of date
 pin-project-lite^0.2.90.2.15up to date
 rkyv^0.7.400.8.8out of date
 serde^1.01.0.214up to date
 smoltcp^0.80.11.0out of date
 socket2^0.40.5.7out of date
 thiserror^11.0.68up to date
 tokio ⚠️^11.41.0maybe insecure
 tokio-serde^0.80.9.0out of date
 tokio-tungstenite^0.210.24.0out of date
 tokio-util^0.7.80.7.12up to date
 tracing^0.10.1.40up to date
 virtual-mio^0.3.00.5.0out of date

Dev dependencies

(3 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 serial_test^2.0.03.1.1out of date
 tokio ⚠️^11.41.0maybe insecure
 tracing-test^0.20.2.5up to date

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On 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.

Workarounds

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);

mio: Tokens for named pipes may be delivered after deregistration

RUSTSEC-2024-0019

Impact

When using named pipes on Windows, mio will under some circumstances return invalid tokens that correspond to named pipes that have already been deregistered from the mio registry. The impact of this vulnerability depends on how mio is used. For some applications, invalid tokens may be ignored or cause a warning or a crash. On the other hand, for applications that store pointers in the tokens, this vulnerability may result in a use-after-free.

For users of Tokio, this vulnerability is serious and can result in a use-after-free in Tokio.

The vulnerability is Windows-specific, and can only happen if you are using named pipes. Other IO resources are not affected.

Affected versions

This vulnerability has been fixed in mio v0.8.11.

All versions of mio between v0.7.2 and v0.8.10 are vulnerable.

Tokio is vulnerable when you are using a vulnerable version of mio AND you are using at least Tokio v1.30.0. Versions of Tokio prior to v1.30.0 will ignore invalid tokens, so they are not vulnerable.

Workarounds

Vulnerable libraries that use mio can work around this issue by detecting and ignoring invalid tokens.

Technical details

When an IO resource registered with mio has a readiness event, mio delivers that readiness event to the user using a user-specified token. Mio guarantees that when an IO resource is deregistered, then it will never return the token for that IO resource again. However, for named pipes on windows, mio may sometimes deliver the token for a named pipe even though the named pipe has been previously deregistered.

This vulnerability was originally reported in the Tokio issue tracker: tokio-rs/tokio#6369
This vulnerability was fixed in: tokio-rs/mio#1760

Thank you to @rofoun and @radekvit for discovering and reporting this issue.