Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RUSTSEC-2023-0001: reject_remote_clients Configuration corruption #15

Open
github-actions bot opened this issue Mar 8, 2023 · 0 comments
Open

Comments

@github-actions
Copy link

github-actions bot commented Mar 8, 2023

reject_remote_clients Configuration corruption

Details
Package tokio
Version 1.19.2
URL GHSA-7rrj-xr53-82p7
Date 2023-01-04
Patched versions >=1.18.4, <1.19.0,>=1.20.3, <1.21.0,>=1.23.1
Unaffected versions <1.7.0

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

See advisory page for additional details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants