This project contains known security vulnerabilities. Find detailed information at the bottom.
attohttpc(16 total, 4 outdated, 2 insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.13 | 0.23.1 | out of date |
| encoding_rs | ^0.8 | 0.8.44 | up to date |
| encoding_rs_io | ^0.1 | 0.1.8 | up to date |
| flate2 | ^1.0 | 1.1.11 | up to date |
| http | ^0.2 | 1.5.0 | out of date |
| log | ^0.4 | 0.4.35 | up to date |
| mime | ^0.3 | 0.3.18 | up to date |
| multipart | ^0.18 | 0.18.0 | up to date |
| native-tls | ^0.2 | 0.2.18 | up to date |
| rustls ⚠️ | ^0.20 | 0.23.46 | insecure |
| serde | ^1 | 1.0.229 | up to date |
| serde_json | ^1 | 1.0.154 | up to date |
| serde_urlencoded | ^0.7 | 0.7.1 | up to date |
| url | ^2 | 2.5.8 | up to date |
| webpki | ^0.22 | 0.22.4 | up to date |
| webpki-roots ⚠️ | ^0.22 | 1.0.11 | insecure |
(10 total, 4 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| anyhow | ^1 | 1.0.104 | up to date |
| env_logger | ^0.9 | 0.11.11 | out of date |
| futures | ^0.3 | 0.3.34 | up to date |
| futures-util | ^0.3 | 0.3.34 | up to date |
| hyper | ^0.14 | 1.12.0 | out of date |
| lazy_static | ^1 | 1.5.1 | up to date |
| tokio | ^1 | 1.54.1 | up to date |
| tokio-rustls | ^0.22 | 0.26.6 | out of date |
| tokio-stream | ^0.1 | 0.1.19 | up to date |
| warp | ^0.3 | 0.4.3 | out of 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.
rustls: Unauthenticated ServerHello can downgrade later connections to classical key exchangeThe client recorded the server-selected key exchange group for each server name when processing the ServerHello, before the server was authenticated. This record is used to predict which key share to send in future ClientHellos to that server name.
A network attacker can answer one connection attempt with a ServerHello
selecting X25519, and then close the connection. Later ClientHellos for that
name carry only an X25519 key share, while supported_groups still lists
X25519MLKEM768 first. If the genuine server accepts that share rather than
sending a HelloRetryRequest for its preferred hybrid group, the handshake
completes with classical-only key exchange and no error. This persists for as
long as the entry stays in the client's session store.
The impact is loss of post-quantum confidentiality for affected connections ("harvest now, decrypt later"). There is no key compromise and no authentication bypass.
The following are not affected:
This behaviour is discussed in draft-ietf-tls-key-share-prediction, so the practical impact depends largely on server policy.
webpki-roots: Bundled root certificates allow trust in distrusted emSign intermediatesAffected versions include emSign ECC Root CA - G3, which can allow certificate
paths through distrusted emSign intermediates.
Affected versions may accept certificate paths containing distrusted emSign intermediate public keys. The private keys corresponding to these intermediates are now well known.
Version 1.0.10+ removes this root.
The webpki-roots 0.26.11 compatibility package contains no independent trust
store and re-exports the roots from its separately resolved 1.x dependency.
That parent dependency must resolve to 1.0.10 or newer; an older parent remains
affected by this advisory.