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, 4 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.130.22.1out of date
 js-sys^0.30.3.77up to date
 log^0.40.4.27up to date
 nom^48.0.0out of date
 openssl ⚠️^0.100.10.73maybe insecure
 rand^0.80.9.1out of date
 serde^1.01.0.219up to date
 serde_bytes^0.110.11.17up to date
 serde_cbor^0.110.11.2up to date
 serde_derive^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 thiserror^1.02.0.12out of date
 wasm-bindgen^0.20.2.100up to date
 web-sys^0.30.3.77up to date

Dev dependencies

(11 total, 7 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 askama^0.100.14.0out of date
 askama_tide^0.130.15.0out of date
 async-std^1.61.13.1up to date
 env_logger^0.8.20.11.8out of date
 funty=1.1.02.0.0out of date
 lru ⚠️^0.60.15.0out of date
 openssl ⚠️^0.100.10.73maybe insecure
 rustls ⚠️^0.19.00.23.28out of date
 structopt^0.30.3.26up to date
 tide^0.160.16.0up to date
 tide-rustls^0.20.3.0out of 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.

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.

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.