This project contains known security vulnerabilities. Find detailed information at the bottom.
trust-dns-proto(35 total, 12 outdated, 4 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| async-trait | ^0.1.43 | 0.1.92 | up to date |
| backtrace | ^0.3.50 | 0.3.76 | up to date |
| bytes | ^1 | 1.12.1 | up to date |
| cfg-if | ^1 | 1.0.5 | up to date |
| data-encoding | ^2.2.0 | 2.11.1 | up to date |
| enum-as-inner | ^0.4 | 0.7.0 | out of date |
| futures-channel | ^0.3.5 | 0.3.34 | up to date |
| futures-io | ^0.3.5 | 0.3.34 | up to date |
| futures-util | ^0.3.5 | 0.3.34 | up to date |
| h2 ⚠️ | ^0.3.0 | 0.4.19 | insecure |
| http | ^0.2 | 1.5.0 | out of date |
| idna ⚠️ | ^0.2.3 | 1.1.0 | insecure |
| ipnet | ^2.3.0 | 2.12.2 | up to date |
| js-sys | ^0.3.44 | 0.3.106 | up to date |
| lazy_static | ^1.2.0 | 1.5.0 | up to date |
| log | ^0.4 | 0.4.34 | up to date |
| native-tls | ^0.2 | 0.2.18 | up to date |
| openssl | ^0.10 | 0.10.81 | up to date |
| rand | ^0.8 | 0.10.3 | out of date |
| ring ⚠️ | ^0.16 | 0.17.14 | insecure |
| rustls ⚠️ | ^0.20.0 | 0.23.45 | insecure |
| rustls-pemfile | ^0.3.0 | 2.2.0 | out of date |
| serde | ^1.0 | 1.0.229 | up to date |
| smallvec | ^1.6 | 1.16.2 | up to date |
| socket2 | ^0.4.0 | 0.6.5 | out of date |
| thiserror | ^1.0.20 | 2.0.21 | out of date |
| tinyvec | ^1.1.1 | 1.13.3 | up to date |
| tokio | ^1.0 | 1.53.1 | up to date |
| tokio-native-tls | ^0.3.0 | 0.3.1 | up to date |
| tokio-openssl | ^0.6.0 | 0.6.5 | up to date |
| tokio-rustls | ^0.23.0 | 0.26.5 | out of date |
| url | ^2.1.0 | 2.5.8 | up to date |
| wasm-bindgen | ^0.2.58 | 0.2.129 | up to date |
| webpki | ^0.22.0 | 0.22.4 | up to date |
| webpki-roots | ^0.22.1 | 1.0.9 | out of date |
(4 total, 1 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| env_logger | ^0.9 | 0.11.11 | out of date |
| futures-executor | ^0.3.5 | 0.3.34 | up to date |
| openssl | ^0.10 | 0.10.81 | up to date |
| tokio | ^1.0 | 1.53.1 | up to date |
rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network inputIf a close_notify alert is received during a handshake, complete_io
does not terminate.
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io
and are not affected.
rustls::Stream and rustls::StreamOwned types use
complete_io and are affected.
idna: `idna` accepts Punycode labels that do not produce any non-ASCII when decodedidna 0.5.0 and earlier accepts Punycode labels that do not produce any non-ASCII output, which means that either ASCII labels or the empty root label can be masked such that they appear unequal without IDNA processing or when processed with a different implementation and equal when processed with idna 0.5.0 or earlier.
Concretely, example.org and xn--example-.org become equal after processing by idna 0.5.0 or earlier. Also, example.org.xn-- and example.org. become equal after processing by idna 0.5.0 or earlier.
In applications using idna (but not in idna itself) this may be able to lead to privilege escalation when host name comparison is part of a privilege check and the behavior is combined with a client that resolves domains with such labels instead of treating them as errors that preclude DNS resolution / URL fetching and with the attacker managing to introduce a DNS entry (and TLS certificate) for an xn---masked name that turns into the name of the target when processed by idna 0.5.0 or earlier.
Upgrade to idna 1.0.3 or later, if depending on idna directly, or to url 2.5.4 or later, if depending on idna via url. (This issue was fixed in idna 1.0.0, but versions earlier than 1.0.3 are not recommended for other reasons.)
When upgrading, please take a moment to read about alternative Unicode back ends for idna.
If you are using Rust earlier than 1.81 in combination with SQLx 0.8.2 or earlier, please also read an issue about combining them with url 2.5.4 and idna 1.0.3.
This issue resulted from idna 0.5.0 and earlier implementing the UTS 46 specification literally on this point and the specification having this bug. The specification bug has been fixed in revision 33 of UTS 46.
Thanks to kageshiron for recognizing the security implications of this behavior.
ring: Some AES functions may panic when overflow checking is enabled.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.
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.