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 actix-http

Dependencies

(37 total, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix-codec^0.4.00.4.2up to date
 actix-rt^2.22.6.0up to date
 actix-service^2.0.02.0.2up to date
 actix-tls^3.0.0-beta.53.0.1up to date
 actix-utils^3.0.03.0.0up to date
 ahash^0.70.7.6up to date
 base64^0.130.13.0up to date
 bitflags^1.21.3.2up to date
 brotli2^0.3.20.3.2up to date
 bytes^11.1.0up to date
 bytestring^11.0.0up to date
 derive_more^0.99.50.99.17up to date
 encoding_rs^0.80.8.30up to date
 flate2^1.0.131.0.22up to date
 futures-core^0.3.70.3.19up to date
 futures-util^0.3.70.3.19up to date
 h2^0.3.10.3.10up to date
 http^0.2.20.2.6up to date
 httparse^1.5.11.5.1up to date
 itoa^0.41.0.1out of date
 language-tags^0.30.3.2up to date
 local-channel^0.10.1.2up to date
 log^0.40.4.14up to date
 mime^0.30.3.16up to date
 once_cell^1.51.9.0up to date
 percent-encoding^2.12.1.0up to date
 pin-project^1.0.01.0.10up to date
 pin-project-lite^0.20.2.8up to date
 rand^0.80.8.4up to date
 regex^1.31.5.4up to date
 serde^1.01.0.133up to date
 sha-1^0.90.10.0out of date
 smallvec^1.6.11.8.0up to date
 time^0.2.230.3.5out of date
 tokio ⚠️^1.21.15.0maybe insecure
 trust-dns-resolver^0.20.00.20.3up to date
 zstd^0.70.9.2+zstd.1.5.1out of date

Security Vulnerabilities

tokio: Data race when sending and receiving after closing a `oneshot` channel

RUSTSEC-2021-0124

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

See tokio#4225 for more details.