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 async-openai

Dependencies

(24 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-openai-macros^0.1.00.1.1up to date
 backoff^0.4.00.4.0up to date
 base64^0.220.22.1up to date
 bytes^1.111.11.0up to date
 derive_builder^0.200.20.2up to date
 eventsource-stream^0.20.2.3up to date
 futures^0.30.3.31up to date
 hex^0.40.4.3up to date
 hmac^0.120.12.1up to date
 rand^0.90.9.2up to date
 reqwest^0.120.13.1out of date
 reqwest-eventsource^0.6.00.6.0up to date
 secrecy^0.100.10.3up to date
 serde^11.0.228up to date
 serde_json^11.0.149up to date
 serde_urlencoded^0.70.7.1up to date
 sha2^0.100.10.9up to date
 thiserror^22.0.17up to date
 tokio ⚠️^11.49.0maybe insecure
 tokio-stream^0.10.1.18up to date
 tokio-tungstenite^0.280.28.0up to date
 tokio-util^0.70.7.18up to date
 tracing^0.10.1.44up to date
 url^2.52.5.8up to date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 serde_json^11.0.149up to date
 tokio-test^0.40.4.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);