Deps.rs

async-nats 0.34.0

[![dependency status](https://deps.rs/crate/async-nats/0.34.0/status.svg)](https://deps.rs/crate/async-nats/0.34.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 async-nats

Dependencies

(25 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.220.22.1up to date
 bytes^1.4.01.10.1up to date
 futures^0.3.280.3.31up to date
 memchr^2.42.7.4up to date
 nkeys^0.40.4.4up to date
 nuid^0.50.5.0up to date
 once_cell^1.18.01.21.3up to date
 portable-atomic^11.11.0up to date
 rand^0.80.9.1out of date
 regex^1.9.11.11.1up to date
 ring ⚠️^0.170.17.14maybe insecure
 rustls-native-certs^0.70.8.1out of date
 rustls-pemfile^22.2.0up to date
 serde^1.0.1841.0.219up to date
 serde_json^1.0.1041.0.140up to date
 serde_nanos^0.1.30.1.4up to date
 serde_repr^0.1.160.1.20up to date
 thiserror^1.02.0.12out of date
 time^0.3.240.3.41up to date
 tokio^1.361.44.2up to date
 tokio-rustls^0.250.26.2out of date
 tracing^0.10.1.41up to date
 tryhard^0.50.5.1up to date
 url^22.5.4up to date
 rustls-webpki^0.1020.103.1out of date

Dev dependencies

(8 total, 3 outdated)

CrateRequiredLatestStatus
 criterion^0.50.5.1up to date
 futures^0.3.280.3.31up to date
 jsonschema^0.17.10.30.0out of date
 num^0.4.10.4.3up to date
 rand^0.80.9.1out of date
 reqwest^0.11.180.12.15out of date
 tokio^1.25.01.44.2up to date
 tracing-subscriber^0.30.3.19up 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.