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 attohttpc

Dependencies

(14 total, 5 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 encoding_rs^0.80.8.34up to date
 encoding_rs_io^0.10.1.7up to date
 flate2^1.01.0.28up to date
 http^0.21.1.0out of date
 log^0.40.4.21up to date
 native-tls^0.20.2.11up to date
 openssl ⚠️^0.10.260.10.64maybe insecure
 rustls^0.160.23.4out of date
 serde^11.0.198up to date
 serde_json^11.0.116up to date
 serde_urlencoded^0.60.7.1out of date
 url^22.5.0up to date
 webpki ⚠️^0.210.22.4out of date
 webpki-roots^0.180.26.1out of date

Dev dependencies

(3 total, 1 outdated)

CrateRequiredLatestStatus
 env_logger^0.70.11.3out of date
 lazy_static^11.4.0up to date
 rouille^33.6.2up to date

Security Vulnerabilities

openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-read

RUSTSEC-2023-0044

When this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.

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

RUSTSEC-2023-0052

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.

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

webpki 0.22.1 included a partial fix and webpki 0.22.2 added further fixes.