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 ureq

Dependencies

(18 total, 9 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 base64^0.210.22.1out of date
 brotli-decompressor^2.3.24.0.1out of date
 cookie^0.170.18.1out of date
 cookie_store^0.200.21.1out of date
 encoding_rs^0.80.8.35up to date
 flate2^1.0.221.0.35up to date
 http^0.21.2.0out of date
 log^0.40.4.22up to date
 native-tls^0.20.2.12up to date
 once_cell^11.20.2up to date
 rustls ⚠️^0.21.60.23.20out of date
 rustls-native-certs^0.60.8.1out of date
 serde^11.0.216up to date
 serde_json>=1.0.971.0.133up to date
 socks^0.30.3.4up to date
 url^22.5.4up to date
 rustls-webpki ⚠️^0.1010.102.8out of date
 webpki-roots^0.250.26.7out of date

Dev dependencies

(4 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 env_logger^0.100.11.6out of date
 rustls ⚠️>=0.21.6, <0.220.23.20out of date
 rustls-pemfile^1.02.2.0out of date
 serde^11.0.216up to date

Security Vulnerabilities

rustls-webpki: rustls-webpki: CPU denial of service in certificate path building

RUSTSEC-2023-0053

When this crate is given a pathological certificate chain to validate, it will spend CPU time exponential with the number of candidate certificates at each step of path building.

Both TLS clients and TLS servers that accept client certificate are affected.

We now give each path building operation a budget of 100 signature verifications.

The original webpki crate is also affected.

This was previously reported in the original crate https://github.com/briansmith/webpki/issues/69 and re-reported to us recently by Luke Malinowski.

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If 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.