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 servo

Dependencies

(65 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 accesskit^0.24.00.24.1up to date
 arboard^33.6.1up to date
 bitflags^2.112.13.0up to date
 cookie^0.180.18.1up to date
 crossbeam-channel^0.50.5.15up to date
 servo-devtools=0.3.00.3.0up to date
 servo-devtools-traits=0.3.00.3.0up to date
 dpi^0.10.1.2up to date
 servo-embedder-traits=0.3.00.3.0up to date
 env_logger^0.110.11.11up to date
 euclid^0.220.22.14up to date
 servo-fonts=0.3.00.3.0up to date
 gaol^0.2.10.2.1up to date
 gstreamer^0.250.25.3up to date
 http^1.41.4.2up to date
 image^0.250.25.10up to date
 ipc-channel^0.220.22.0up to date
 keyboard-types^0.8.30.8.3up to date
 servo-layout=0.3.00.3.0up to date
 servo-layout-api=0.3.00.3.0up to date
 log^0.4.300.4.33up to date
 servo-media-thread=0.3.00.3.0up to date
 mozangle^0.5.50.5.5up to date
 servo-net=0.3.00.3.0up to date
 servo-net-traits=0.3.00.3.0up to date
 servo-paint=0.3.00.3.0up to date
 servo-paint-api=0.3.00.3.0up to date
 parking_lot^0.120.12.5up to date
 servo-profile=0.3.00.3.0up to date
 servo-profile-traits=0.3.00.3.0up to date
 rustc-hash^2.1.22.1.2up to date
 servo-script=0.3.00.3.0up to date
 servo-script-traits=0.3.00.3.0up to date
 serde^1.0.2281.0.228up to date
 servo-background-hang-monitor=0.3.00.3.0up to date
 servo-base=0.3.00.3.0up to date
 servo-bluetooth=0.3.00.3.0up to date
 servo-bluetooth-traits=0.3.00.3.0up to date
 servo-canvas-traits=0.3.00.3.0up to date
 servo-config=0.3.00.3.0up to date
 servo-constellation=0.3.00.3.0up to date
 servo-constellation-traits=0.3.00.3.0up to date
 servo-default-resources=0.3.00.3.0up to date
 servo-geometry=0.3.00.3.0up to date
 servo-media=0.3.00.3.0up to date
 servo-media-dummy=0.3.00.3.0up to date
 servo-media-gstreamer=0.3.00.3.0up to date
 servo-media-ohos=0.3.00.3.0up to date
 servo-tracing=0.3.00.3.0up to date
 servo-url=0.3.00.3.0up to date
 servo-wakelock=0.3.00.3.0up to date
 servo-storage=0.3.00.3.0up to date
 servo-storage-traits=0.3.00.3.0up to date
 stylo^0.18.00.18.0up to date
 stylo_traits^0.18.00.18.0up to date
 surfman^0.12.10.13.0out of date
 tokio ⚠️^11.52.3maybe insecure
 tracing^0.1.440.1.44up to date
 url^2.52.5.8up to date
 servo-webgl=0.3.00.3.0up to date
 servo-webgpu=0.3.00.3.0up to date
 webrender^0.680.69.0out of date
 webrender_api^0.680.69.0out of date
 servo-webxr=0.3.00.3.0up to date
 servo-webxr-api=0.3.00.3.0up to date

Dev dependencies

(10 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 accesskit_consumer^0.35.00.37.0out of date
 content-security-policy^0.8.00.8.0up to date
 http^1.41.4.2up to date
 http-body-util^0.10.1.3up to date
 hyper^1.101.10.1up to date
 itertools^0.140.15.0out of date
 servo-net=0.3.00.3.0up to date
 rustls ⚠️^0.230.23.41maybe insecure
 tracing^0.1.440.1.44up to date
 winit^0.30.130.30.13up 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);

rustls: rustls network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.