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 webauthn-rs

Dependencies

(14 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.130.22.0out of date
 js-sys^0.30.3.69up to date
 nom^7.17.1.3up to date
 openssl ⚠️^0.100.10.64maybe insecure
 rand^0.80.8.5up to date
 serde^1.01.0.197up to date
 serde_cbor^0.110.11.2up to date
 serde_derive^1.01.0.197up to date
 serde_json^1.01.0.115up to date
 thiserror^1.01.0.58up to date
 tracing^0.10.1.40up to date
 url^22.5.0up to date
 wasm-bindgen^0.20.2.92up to date
 web-sys^0.30.3.69up to date

Dev dependencies

(10 total, 4 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 askama^0.110.12.1out of date
 askama_tide^0.140.15.0out of date
 async-std^1.61.12.0up to date
 lru ⚠️^0.70.12.3out of date
 openssl ⚠️^0.100.10.64maybe insecure
 rustls^0.19.00.23.4out of date
 structopt^0.30.3.26up to date
 tide^0.160.16.0up to date
 tide-rustls^0.30.3.0up to date
 tracing-subscriber^0.30.3.18up to date

Security Vulnerabilities

lru: Use after free in lru crate

RUSTSEC-2021-0130

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