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 turn-server-proto

Dependencies

(10 total, 3 possibly insecure)

CrateRequiredLatestStatus
 byteorder^11.5.0up to date
 openssl ⚠️^0.100.10.74maybe insecure
 pnet_packet^0.350.35.0up to date
 rand^0.90.9.2up to date
 rustls ⚠️^0.230.23.32maybe insecure
 smallvec ⚠️^11.15.1maybe insecure
 stun-proto^1.0.01.0.0up to date
 thiserror^22.0.17up to date
 tracing^0.10.1.41up to date
 turn-types^0.4.00.4.0up to date

Dev dependencies

(4 total, 1 possibly insecure)

CrateRequiredLatestStatus
 criterion^0.70.7.0up to date
 rustls ⚠️^0.230.23.32maybe insecure
 tracing^0.10.1.41up to date
 tracing-subscriber^0.30.3.20up to date

Security Vulnerabilities

smallvec: Buffer overflow in SmallVec::insert_many

RUSTSEC-2021-0003

A bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.

This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.

The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.

Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.

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.