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 dog

Dependencies

(6 total, all up-to-date)

CrateRequiredLatestStatus
 ansi_term^0.120.12.1up to date
 atty^0.20.2.14up to date
 getopts^0.20.2.21up to date
 rand^0.80.8.5up to date
 json^0.120.12.4up to date
 log^0.40.4.21up to date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 pretty_assertions^0.71.4.0out of date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 datetime^0.5.10.5.2up to date

Crate dns

Dependencies

(4 total, 1 outdated)

CrateRequiredLatestStatus
 log^0.40.4.21up to date
 byteorder^1.31.5.0up to date
 base64^0.130.22.0out of date
 unic-idna^0.9.00.9.0up to date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 pretty_assertions^0.71.4.0out of date

Crate dns-transport

Dependencies

(7 total, 3 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 log^0.40.4.21up to date
 native-tls^0.20.2.11up to date
 httparse^1.31.8.0up to date
 rustls^0.190.23.4out of date
 webpki ⚠️^0.21.00.22.4out of date
 webpki-roots^0.21.00.26.1out of date
 cfg-if^11.0.0up to date

Security Vulnerabilities

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.