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.
webauthn-rs(14 total, 2 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.13 | 0.22.0 | out of date |
| js-sys | ^0.3 | 0.3.69 | up to date |
| log | ^0.4 | 0.4.21 | up to date |
| nom | ^4 | 7.1.3 | out of date |
| openssl ⚠️ | ^0.10 | 0.10.64 | maybe insecure |
| rand | ^0.8 | 0.8.5 | up to date |
| serde | ^1.0 | 1.0.198 | up to date |
| serde_bytes | ^0.11 | 0.11.14 | up to date |
| serde_cbor | ^0.11 | 0.11.2 | up to date |
| serde_derive | ^1.0 | 1.0.198 | up to date |
| serde_json | ^1.0 | 1.0.116 | up to date |
| thiserror | ^1.0 | 1.0.59 | up to date |
| wasm-bindgen | ^0.2 | 0.2.92 | up to date |
| web-sys | ^0.3 | 0.3.69 | up to date |
(11 total, 7 outdated, 3 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| askama | ^0.10 | 0.12.1 | out of date |
| askama_tide | ^0.13 | 0.15.0 | out of date |
| async-std | ^1.6 | 1.12.0 | up to date |
| env_logger | ^0.8.2 | 0.11.3 | out of date |
| funty | =1.1.0 | 2.0.0 | out of date |
| lru ⚠️ | ^0.6 | 0.12.3 | out of date |
| openssl ⚠️ | ^0.10 | 0.10.64 | maybe insecure |
| rustls ⚠️ | ^0.19.0 | 0.23.5 | out of date |
| structopt | ^0.3 | 0.3.26 | up to date |
| tide | ^0.16 | 0.16.0 | up to date |
| tide-rustls | ^0.2 | 0.3.0 | out of date |
lru: Use after free in lru crateLru crate has use after free vulnerability.
Lru crate has two functions for getting an iterator. Both iterators give references to key and value. Calling specific functions, like pop(), will remove and free the value, and but it's still possible to access the reference of value which is already dropped causing use after free.
openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-readWhen this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.
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.