Deps.rs

x509-parser 0.15.1

[![dependency status](https://deps.rs/crate/x509-parser/0.15.1/status.svg)](https://deps.rs/crate/x509-parser/0.15.1)

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 x509-parser

Dependencies

(10 total, 7 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 asn1-rs^0.50.7.1out of date
 data-encoding^2.2.12.9.0up to date
 der-parser^8.1.010.0.0out of date
 lazy_static^1.41.5.0up to date
 nom^7.08.0.0out of date
 oid-registry^0.60.8.1out of date
 ring ⚠️^0.16.110.17.14out of date
 rusticata-macros^4.05.0.0out of date
 thiserror^1.0.22.0.12out of date
 time^0.3.70.3.41up 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.