Deps.rs

servo-malloc-size-of 0.3.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 servo-malloc-size-of

Dependencies

(35 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 app_units^0.70.7.8up to date
 atomic_refcell^0.1.140.1.14up to date
 content-security-policy^0.8.00.8.0up to date
 crossbeam-channel^0.50.5.15up to date
 data-url^0.30.3.2up to date
 encoding_rs^0.80.8.35up to date
 euclid^0.220.22.14up to date
 http^1.41.4.2up to date
 icu_locid^1.5.02.0.0out of date
 indexmap^2.14.02.14.0up to date
 ipc-channel^0.220.22.0up to date
 keyboard-types^0.8.30.8.3up to date
 markup5ever^0.390.39.0up to date
 mime^0.3.130.3.17up to date
 parking_lot^0.120.12.5up to date
 resvg^0.47.00.47.0up to date
 servo-allocator=0.3.00.3.0up to date
 servo_arc^0.4.30.4.3up to date
 smallvec^1.151.15.2up to date
 string_cache^0.90.9.0up to date
 stylo^0.18.00.18.0up to date
 stylo_dom^0.18.00.18.0up to date
 stylo_malloc_size_of^0.18.00.18.0up to date
 taffy^0.10.10.11.0out of date
 tendril^0.50.5.0up to date
 time ⚠️^0.30.3.52maybe insecure
 tokio ⚠️^11.52.3maybe insecure
 unicode-bidi^0.3.180.3.18up to date
 unicode-script^0.50.5.8up to date
 url^2.52.5.8up to date
 urlpattern^0.30.6.0out of date
 uuid^1.23.11.23.4up to date
 webrender^0.680.69.0out of date
 webrender_api^0.680.69.0out of date
 wr_malloc_size_of^0.2.20.2.2up 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);

time: Denial of Service via Stack Exhaustion

RUSTSEC-2026-0009

Impact

When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.

Patches

A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.

Workarounds

Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.