This project contains known security vulnerabilities. Find detailed information at the bottom.
actix-http(41 total, 19 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| actix | >=0.10.0, <0.11.0 | 0.13.5 | out of date |
| actix-codec | >=0.3.0, <0.4.0 | 0.5.4 | out of date |
| actix-connect | >=2.0.0, <3.0.0 | 2.0.0 | up to date |
| actix-rt | >=1.0.0, <2.0.0 | 2.15.0 | out of date |
| actix-service | >=1.0.6, <2.0.0 | 2.0.3 | out of date |
| actix-threadpool | >=0.3.1, <0.4.0 | 0.3.3 | up to date |
| actix-tls | >=2.0.0, <3.0.0 | 3.6.0 | out of date |
| actix-utils | >=2.0.0, <3.0.0 | 3.0.2 | out of date |
| base64 | >=0.13.0, <0.14.0 | 0.23.1 | out of date |
| bitflags | >=1.2.0, <2.0.0 | 2.13.2 | out of date |
| brotli2 | >=0.3.2, <0.4.0 | 0.3.2 | up to date |
| bytes | >=0.5.3, <0.6.0 | 1.12.1 | out of date |
| cookie | >=0.14.1, <0.15.0 | 0.18.2 | out of date |
| copyless | >=0.1.4, <0.2.0 | 0.1.5 | up to date |
| derive_more | >=0.99.2, <0.100.0 | 2.1.1 | out of date |
| either | >=1.5.3, <2.0.0 | 1.18.0 | up to date |
| encoding_rs | >=0.8.0, <0.9.0 | 0.8.41 | up to date |
| flate2 | >=1.0.13, <2.0.0 | 1.1.10 | up to date |
| futures-channel | >=0.3.5, <0.4.0 | 0.3.34 | up to date |
| futures-core | >=0.3.5, <0.4.0 | 0.3.34 | up to date |
| futures-util | >=0.3.5, <0.4.0 | 0.3.34 | up to date |
| fxhash | >=0.2.1, <0.3.0 | 0.2.1 | up to date |
| h2 ⚠️ | >=0.2.1, <0.3.0 | 0.4.19 | insecure |
| http | >=0.2.0, <0.3.0 | 1.5.0 | out of date |
| httparse | >=1.3.0, <2.0.0 | 1.10.1 | up to date |
| indexmap | >=1.3.0, <2.0.0 | 2.14.2 | out of date |
| itoa | >=0.4.0, <0.5.0 | 1.0.18 | out of date |
| language-tags | >=0.2.0, <0.3.0 | 0.3.2 | out of date |
| lazy_static | >=1.4.0, <2.0.0 | 1.5.0 | up to date |
| log | >=0.4.0, <0.5.0 | 0.4.34 | up to date |
| mime | >=0.3.0, <0.4.0 | 0.3.17 | up to date |
| percent-encoding | >=2.1.0, <3.0.0 | 2.3.2 | up to date |
| pin-project | >=1.0.0, <2.0.0 | 1.1.13 | up to date |
| rand | >=0.7.0, <0.8.0 | 0.10.3 | out of date |
| regex | >=1.3.0, <2.0.0 | 1.13.1 | up to date |
| serde | >=1.0.0, <2.0.0 | 1.0.229 | up to date |
| serde_json | >=1.0.0, <2.0.0 | 1.0.151 | up to date |
| serde_urlencoded | >=0.7.0, <0.8.0 | 0.7.1 | up to date |
| sha-1 | >=0.9.0, <0.10.0 | 0.10.1 | out of date |
| slab | >=0.4.0, <0.5.0 | 0.4.12 | up to date |
| time | >=0.2.7, <0.3.0 | 0.3.55 | out of date |
h2: Resource exhaustion vulnerability in h2 may lead to Denial of Service (DoS)If an attacker is able to flood the network with pairs of HEADERS/RST_STREAM frames, such that the h2 application is not able to accept them faster than the bytes are received, the pending accept queue can grow in memory usage. Being able to do this consistently can result in excessive memory use, and eventually trigger Out Of Memory.
This flaw is corrected in hyperium/h2#668, which restricts remote reset stream count by default.
h2: Resource exhaustion vulnerability in h2 may lead to Denial of Service (DoS)An attacker with an HTTP/2 connection to an affected endpoint can send a steady stream of invalid frames to force the generation of reset frames on the victim endpoint. By closing their recv window, the attacker could then force these resets to be queued in an unbounded fashion, resulting in Out Of Memory (OOM) and high CPU usage.
This fix is corrected in hyperium/h2#737, which limits the total number of internal error resets emitted by default before the connection is closed.
h2: Degradation of service in h2 servers with CONTINUATION FloodAn 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.
h2: h2 unbounded empty DATA framesThe h2 crate, used internally by hyper, had a flaw that would accept and queue empty DATA frames without limit. If streams were not actively drained, this could lead to unbounded memory usage, or a panic if the length overflows.
Low severity.
Patched in v0.4.16.