This project contains known security vulnerabilities. Find detailed information at the bottom.
aws-smithy-runtime(23 total, 7 outdated, 1 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| aws-smithy-async | ^1.2.1 | 1.3.0 | up to date |
| aws-smithy-http | ^0.60.11 | 0.64.0 | out of date |
| aws-smithy-protocol-test | ^0.63.0 | 0.64.0 | out of date |
| aws-smithy-runtime-api | ^1.7.2 | 1.17.0 | up to date |
| aws-smithy-types | ^1.2.7 | 1.8.0 | up to date |
| bytes | ^1 | 1.12.1 | up to date |
| fastrand | ^2.0.0 | 2.5.0 | up to date |
| h2 ⚠️ | ^0.3 | 0.4.19 | insecure |
| http | ^0.2.8 | 1.5.0 | out of date |
| http-body | ^1 | 1.1.0 | up to date |
| httparse | ^1.8.0 | 1.10.1 | up to date |
| hyper | ^0.14.26 | 1.11.1 | out of date |
| hyper-rustls | ^0.24 | 0.27.10 | out of date |
| indexmap | ^2 | 2.14.2 | up to date |
| once_cell | ^1.18.0 | 1.21.4 | up to date |
| pin-project-lite | ^0.2.7 | 0.2.17 | up to date |
| pin-utils | ^0.1.0 | 0.1.0 | up to date |
| rustls | ^0.21.8 | 0.23.45 | out of date |
| serde | ^1 | 1.0.229 | up to date |
| serde_json | ^1 | 1.0.151 | up to date |
| tokio | ^1.25 | 1.53.1 | up to date |
| tracing | ^0.1.37 | 0.1.44 | up to date |
| tracing-subscriber | ^0.3.16 | 0.3.23 | up to date |
(12 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| approx | ^0.5.1 | 0.5.1 | up to date |
| aws-smithy-async | ^1.2.1 | 1.3.0 | up to date |
| aws-smithy-runtime-api | ^1.7.2 | 1.17.0 | up to date |
| aws-smithy-types | ^1.2.7 | 1.8.0 | up to date |
| fastrand | ~2.0.0 | 2.5.0 | out of date |
| futures-util | ^0.3.29 | 0.3.34 | up to date |
| http | ^1 | 1.5.0 | up to date |
| hyper | ^0.14.27 | 1.11.1 | out of date |
| pretty_assertions | ^1.4.0 | 1.4.1 | up to date |
| tokio | ^1.25 | 1.53.1 | up to date |
| tracing-subscriber | ^0.3.16 | 0.3.23 | up to date |
| tracing-test | ^0.2.1 | 0.2.6 | up to date |
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.