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.
aws-smithy-runtime(22 total, 5 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| aws-smithy-async | ^1.2.1 | 1.2.1 | up to date |
| aws-smithy-http | ^0.60.8 | 0.60.8 | up to date |
| aws-smithy-protocol-test | ^0.60.7 | 0.60.7 | up to date |
| aws-smithy-runtime-api | ^1.4.0 | 1.5.0 | up to date |
| aws-smithy-types | ^1.1.8 | 1.1.8 | up to date |
| bytes | ^1 | 1.6.0 | up to date |
| fastrand | ^2.0.0 | 2.1.0 | up to date |
| h2 ⚠️ | ^0.3 | 0.4.4 | out of date |
| http | ^0.2.8 | 1.1.0 | out of date |
| http-body | ^1 | 1.0.0 | up to date |
| hyper | ^0.14.26 | 1.3.1 | out of date |
| hyper-rustls | ^0.24 | 0.27.1 | out of date |
| indexmap | ^2 | 2.2.6 | up to date |
| once_cell | ^1.18.0 | 1.19.0 | up to date |
| pin-project-lite | ^0.2.7 | 0.2.14 | up to date |
| pin-utils | ^0.1.0 | 0.1.0 | up to date |
| rustls ⚠️ | ^0.21.8 | 0.23.5 | out of date |
| serde | ^1 | 1.0.200 | up to date |
| serde_json | ^1 | 1.0.116 | up to date |
| tokio | ^1.25 | 1.37.0 | up to date |
| tracing | ^0.1.37 | 0.1.40 | up to date |
| tracing-subscriber | ^0.3.16 | 0.3.18 | up to date |
(11 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| approx | ^0.5.1 | 0.5.1 | up to date |
| aws-smithy-async | ^1.2.1 | 1.2.1 | up to date |
| aws-smithy-runtime-api | ^1.4.0 | 1.5.0 | up to date |
| aws-smithy-types | ^1.1.8 | 1.1.8 | up to date |
| futures-util | ^0.3.29 | 0.3.30 | up to date |
| http | ^1 | 1.1.0 | up to date |
| hyper | ^0.14.27 | 1.3.1 | out of date |
| pretty_assertions | ^1.4.0 | 1.4.0 | up to date |
| tokio | ^1.25 | 1.37.0 | up to date |
| tracing-subscriber | ^0.3.16 | 0.3.18 | up to date |
| tracing-test | ^0.2.1 | 0.2.4 | up to date |
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.
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.