Deps.rs

ystreet / librice

[![dependency status](https://deps.rs/repo/github/ystreet/librice/status.svg)](https://deps.rs/repo/github/ystreet/librice)

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 rice-proto

Dependencies

(5 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 libc^0.20.2.177up to date
 nom^88.0.0up to date
 openssl ⚠️^0.100.10.74maybe insecure
 rustls ⚠️^0.230.23.35maybe insecure
 rustls-platform-verifier^0.50.6.2out of date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 turn-server-proto^0.4.0-alpha20.4.1up to date

Crate librice

Dependencies

(6 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures^0.30.3.31up to date
 futures-timer^33.0.3up to date
 tracing-futures^0.20.2.5up to date
 smol^22.0.2up to date
 async-io^22.6.0up to date
 tokio ⚠️^11.48.0maybe insecure

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 clap^44.5.51up to date

Crate rice-io

Dependencies

(6 total, all up-to-date)

CrateRequiredLatestStatus
 async-io^22.6.0up to date
 async-lock^33.4.1up to date
 async-task^44.7.1up to date
 flume^0.110.11.1up to date
 futures-lite^22.6.1up to date
 libc^0.20.2.177up to date

Crate rice-c

Dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 sans-io-time^0.10.1.2up to date

Build dependencies

(2 total, 1 outdated)

CrateRequiredLatestStatus
 system-deps^6.07.0.7out of date
 bindgen^0.720.72.1up to date

Crate rice-stun-types

No external dependencies! 🙌

Crate rice-ctypes

No external dependencies! 🙌

Crate rice-fuzz

Dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 libfuzzer-sys^0.40.4.10up 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.

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.