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 gitlab

Dependencies

(25 total, 9 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 async-trait~0.1.90.1.80up to date
 base64~0.130.22.0out of date
 bytes^1.01.6.0up to date
 chrono~0.4.230.4.38up to date
 cron~0.120.12.1up to date
 derive_builder~0.11.20.20.0out of date
 futures-util^0.3.140.3.30up to date
 graphql_client~0.110.14.0out of date
 h2 ⚠️^0.3.240.4.4out of date
 http~0.2.51.1.0out of date
 itertools~0.100.12.1out of date
 log~0.4.60.4.21up to date
 memoffset^0.6.20.9.1out of date
 mio^0.8.110.8.11up to date
 openssl~0.10.600.10.64up to date
 percent-encoding^2.02.3.1up to date
 reqwest~0.11.190.12.4out of date
 rustls-webpki^0.101.40.102.3out of date
 serde~1.0.1031.0.198up to date
 serde_json^1.0.701.0.116up to date
 serde_urlencoded~0.70.7.1up to date
 tempfile^3.4.03.10.1up to date
 thiserror^1.0.21.0.59up to date
 url^2.12.5.0up to date
 void^1.0.11.0.2up to date

Dev dependencies

(2 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 itertools~0.100.12.1out of date
 tokio ⚠️^1.18.51.37.0maybe insecure

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

h2: Degradation of service in h2 servers with CONTINUATION Flood

RUSTSEC-2024-0332

An attacker can send a flood of CONTINUATION frames, causing h2 to process them indefinitely. This results in an increase in CPU usage.

Tokio task budget helps prevent this from a complete denial-of-service, as the server can still respond to legitimate requests, albeit with increased latency.

More details at "https://seanmonstar.com/blog/hyper-http2-continuation-flood/.

Patches available for 0.4.x and 0.3.x versions.