Deps.rs

poem 3.1.7

[![dependency status](https://deps.rs/crate/poem/3.1.7/status.svg)](https://deps.rs/crate/poem/3.1.7)

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 poem

Dependencies

(70 total, 12 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.01.0.97up to date
 async-compression^0.4.00.4.20up to date
 base64^0.22.00.22.1up to date
 bytes^1.1.01.10.1up to date
 chrono^0.4.310.4.40up to date
 eyre^0.6.120.6.12up to date
 fluent^0.16.00.16.1up to date
 fluent-langneg^0.13.00.14.1out of date
 fluent-syntax^0.11.00.11.1up to date
 futures-util^0.3.170.3.31up to date
 headers^0.4.00.4.0up to date
 hex^0.40.4.3up to date
 http^1.0.01.3.1up to date
 http-body-util^0.1.00.1.3up to date
 httpdate^1.0.21.0.3up to date
 hyper^1.0.01.6.0up to date
 hyper-util^0.1.60.1.10up to date
 intl-memoizer^0.5.10.5.2up to date
 cookie^0.180.18.1up to date
 csrf^0.4.10.5.0out of date
 opentelemetry^0.28.00.28.0up to date
 prometheus^0.13.00.13.4up to date
 tempfile^3.2.03.19.0up to date
 mime^0.3.160.3.17up to date
 mime_guess^2.0.32.0.5up to date
 multer^3.0.03.1.0up to date
 nix^0.29.00.29.0up to date
 openssl^0.10.710.10.71up to date
 opentelemetry-http^0.28.00.28.0up to date
 opentelemetry-prometheus^0.28.00.28.0up to date
 opentelemetry-semantic-conventions^0.28.00.28.0up to date
 parking_lot^0.12.00.12.3up to date
 percent-encoding^2.1.02.3.1up to date
 pin-project-lite^0.2.70.2.16up to date
 poem-derive^3.1.03.1.4up to date
 priority-queue^2.0.22.2.2up to date
 quick-xml^0.36.10.37.2out of date
 rand^0.8.40.9.0out of date
 rcgen^0.12.00.13.2out of date
 redis^0.280.29.1out of date
 regex^1.5.51.11.1up to date
 reqwest^0.12.20.12.14up to date
 rfc7239^0.1.00.1.3up to date
 ring ⚠️^0.17.70.17.14maybe insecure
 rust-embed^8.08.6.0up to date
 rustls-pemfile^2.0.02.2.0up to date
 serde^1.0.1301.0.219up to date
 serde_json^1.0.681.0.140up to date
 serde_urlencoded^0.7.10.7.1up to date
 serde_yaml^0.90.9.34+deprecatedup to date
 smallvec^1.6.11.14.0up to date
 sonic-rs^0.3.50.4.0out of date
 sse-codec^0.3.20.3.2up to date
 sync_wrapper^1.0.01.0.2up to date
 thiserror^2.02.0.12up to date
 time^0.30.3.39up to date
 tokio^1.39.11.44.1up to date
 tokio-metrics^0.3.00.4.0out of date
 tokio-native-tls^0.3.00.3.1up to date
 tokio-openssl^0.6.30.6.5up to date
 tokio-rustls^0.25.00.26.2out of date
 tokio-stream^0.1.80.1.17up to date
 tokio-tungstenite^0.250.26.2out of date
 tokio-util^0.7.00.7.14up to date
 tower^0.4.80.5.2out of date
 tracing^0.1.360.1.41up to date
 unic-langid^0.9.00.9.5up to date
 uuid^1.8.01.15.1up to date
 wildmatch^22.4.0up to date
 x509-parser^0.16.00.17.0out of date

Dev dependencies

(2 total, all up-to-date)

CrateRequiredLatestStatus
 async-stream^0.3.20.3.6up to date
 tokio^1.39.11.44.1up to date

Security Vulnerabilities

ring: Some AES functions may panic when overflow checking is enabled.

RUSTSEC-2025-0009

ring::aead::quic::HeaderProtectionKey::new_mask() may panic when overflow checking is enabled. In the QUIC protocol, an attacker can induce this panic by sending a specially-crafted packet. Even unintentionally it is likely to occur in 1 out of every 2**32 packets sent and/or received.

On 64-bit targets operations using ring::aead::{AES_128_GCM, AES_256_GCM} may panic when overflow checking is enabled, when encrypting/decrypting approximately 68,719,476,700 bytes (about 64 gigabytes) of data in a single chunk. Protocols like TLS and SSH are not affected by this because those protocols break large amounts of data into small chunks. Similarly, most applications will not attempt to encrypt/decrypt 64GB of data in one chunk.

Overflow checking is not enabled in release mode by default, but RUSTFLAGS="-C overflow-checks" or overflow-checks = true in the Cargo.toml profile can override this. Overflow checking is usually enabled by default in debug mode.