actix-http 3.7.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 `actix-http`

Dependencies

(32 total, 5 outdated, 1 possibly insecure)

Crate	Required	Latest	Status
actix-codec	`^0.5`	`0.5.2`	up to date
actix-rt	`^2.2`	`2.10.0`	up to date
actix-service	`^2`	`2.0.3`	up to date
actix-tls	`^3.4`	`3.4.0`	up to date
actix-utils	`^3`	`3.0.1`	up to date
ahash	`^0.8`	`0.8.12`	up to date
base64	`^0.22`	`0.22.1`	up to date
bitflags	`^2`	`2.9.1`	up to date
brotli	`^6`	`8.0.1`	out of date
bytes	`^1`	`1.10.1`	up to date
bytestring	`^1`	`1.4.0`	up to date
derive_more	`^0.99.5`	`2.0.1`	out of date
encoding_rs	`^0.8`	`0.8.35`	up to date
flate2	`^1.0.13`	`1.1.2`	up to date
futures-core	`^0.3.17`	`0.3.31`	up to date
h2 ⚠️	`^0.3.24`	`0.4.11`	out of date
http	`^0.2.7`	`1.3.1`	out of date
httparse	`^1.5.1`	`1.10.1`	up to date
httpdate	`^1.0.1`	`1.0.3`	up to date
itoa	`^1`	`1.0.15`	up to date
language-tags	`^0.3`	`0.3.2`	up to date
local-channel	`^0.1`	`0.1.5`	up to date
mime	`^0.3.4`	`0.3.17`	up to date
percent-encoding	`^2.1`	`2.3.1`	up to date
pin-project-lite	`^0.2`	`0.2.16`	up to date
rand	`^0.8`	`0.9.1`	out of date
sha1	`^0.10`	`0.10.6`	up to date
smallvec	`^1.6.1`	`1.15.1`	up to date
tokio	`^1.24.2`	`1.46.1`	up to date
tokio-util	`^0.7`	`0.7.15`	up to date
tracing	`^0.1.30`	`0.1.41`	up to date
zstd	`^0.13`	`0.13.3`	up to date

Dev dependencies

(21 total, 2 outdated, 3 possibly insecure)

Crate	Required	Latest	Status
actix-http-test	`^3`	`3.2.0`	up to date
actix-server	`^2`	`2.6.0`	up to date
actix-tls	`^3.4`	`3.4.0`	up to date
actix-web	`^4`	`4.11.0`	up to date
async-stream	`^0.3`	`0.3.6`	up to date
criterion	`^0.5`	`0.6.0`	out of date
divan	`^0.1.8`	`0.1.21`	up to date
env_logger	`^0.11`	`0.11.8`	up to date
futures-util	`^0.3.17`	`0.3.31`	up to date
memchr	`^2.4`	`2.7.5`	up to date
once_cell	`^1.9`	`1.21.3`	up to date
rcgen	`^0.13`	`0.14.2`	out of date
regex ⚠️	`^1.3`	`1.11.1`	maybe insecure
rustls-pemfile	`^2`	`2.2.0`	up to date
rustversion	`^1`	`1.0.21`	up to date
serde	`^1.0`	`1.0.219`	up to date
serde_json	`^1.0`	`1.0.141`	up to date
static_assertions	`^1`	`1.1.0`	up to date
openssl ⚠️	`^0.10.55`	`0.10.73`	maybe insecure
rustls ⚠️	`^0.23`	`0.23.29`	maybe insecure
tokio	`^1.24.2`	`1.46.1`	up to date

Security Vulnerabilities

`regex`: Regexes with large repetitions on empty sub-expressions take a very long time to parse

RUSTSEC-2022-0013

The Rust Security Response WG was notified that the regex crate did not properly limit the complexity of the regular expressions (regex) it parses. An attacker could use this security issue to perform a denial of service, by sending a specially crafted regex to a service accepting untrusted regexes. No known vulnerability is present when parsing untrusted input with trusted regexes.

This issue has been assigned CVE-2022-24713. The severity of this vulnerability is "high" when the regex crate is used to parse untrusted regexes. Other uses of the regex crate are not affected by this vulnerability.

Overview

The regex crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted regexes. Those (tunable) mitigations already provide sane defaults to prevent attacks. This guarantee is documented and it's considered part of the crate's API.

Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.

Affected versions

All versions of the regex crate before or equal to 1.5.4 are affected by this issue. The fix is include starting from regex 1.5.5.

Mitigations

We recommend everyone accepting user-controlled regexes to upgrade immediately to the latest version of the regex crate.

Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.

Acknowledgements

We want to thank Addison Crump for responsibly disclosing this to us according to the Rust security policy, and for helping review the fix.

We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory.

`h2`: Degradation of service in h2 servers with CONTINUATION Flood

RUSTSEC-2024-0332

An attacker can send a flood of CONTINUATION frames, causing h2 to process them indefinitely. This results in an increase in CPU usage.

Tokio task budget helps prevent this from a complete denial-of-service, as the server can still respond to legitimate requests, albeit with increased latency.

More details at "https://seanmonstar.com/blog/hyper-http2-continuation-flood/.

Patches available for 0.4.x and 0.3.x versions.

`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.