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 wascap

Dependencies

(18 total, 7 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 base64^0.11.00.22.1out of date
 chrono ⚠️^0.4.100.4.41maybe insecure
 chrono-humanize^0.0.110.2.3out of date
 data-encoding^2.1.22.9.0up to date
 env_logger^0.7.10.11.8out of date
 exitfailure^0.5.10.5.1up to date
 lazy_static^1.4.01.5.0up to date
 log^0.4.80.4.27up to date
 nkeys^0.0.80.4.5out of date
 nuid^0.2.10.5.0out of date
 parity-wasm^0.41.00.45.0out of date
 quicli^0.40.4.0up to date
 ring ⚠️^0.16.110.17.14out of date
 serde^11.0.219up to date
 serde_derive^11.0.219up to date
 serde_json^1.0.481.0.140up to date
 structopt^0.3.90.3.26up to date
 term-table^1.2.01.4.0up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

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.