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.
yubihsm(29 total, 22 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| aes | ^0.7 | 0.8.4 | out of date |
| anomaly | ^0.2 | 0.99.0 | out of date |
| bitflags | ^1 | 2.9.1 | out of date |
| block-modes | ^0.8 | 0.9.1 | out of date |
| ccm | ^0.4 | 0.5.0 | out of date |
| chrono ⚠️ | ^0.4 | 0.4.41 | maybe insecure |
| cmac | ^0.6 | 0.7.2 | out of date |
| digest | ^0.9 | 0.10.7 | out of date |
| ecdsa | ^0.12 | 0.16.9 | out of date |
| ed25519 | ^1 | 2.2.3 | out of date |
| ed25519-dalek ⚠️ | ^1 | 2.1.1 | out of date |
| harp | ^0.1 | N/A | up to date |
| hmac | ^0.11 | 0.12.1 | out of date |
| k256 | ^0.9 | 0.13.4 | out of date |
| log | ^0.4 | 0.4.27 | up to date |
| p256 | ^0.9 | 0.13.2 | out of date |
| p384 | ^0.8 | 0.13.1 | out of date |
| pbkdf2 | ^0.8 | 0.12.2 | out of date |
| rand_core | ^0.6 | 0.9.3 | out of date |
| rusb | ^0.8 | 0.9.4 | out of date |
| serde | ^1 | 1.0.219 | up to date |
| serde_json | ^1 | 1.0.140 | up to date |
| sha2 | ^0.9 | 0.10.9 | out of date |
| signature | ^1.2.0 | 2.2.0 | out of date |
| subtle | ^2 | 2.6.1 | up to date |
| thiserror | ^1 | 2.0.12 | out of date |
| tiny_http | ^0.8 | 0.12.0 | out of date |
| uuid | ^0.8 | 1.17.0 | out of date |
| zeroize | ^1 | 1.8.1 | up to date |
(4 total, 3 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.3 | 0.6.0 | out of date |
| ed25519-dalek ⚠️ | ^1 | 2.1.1 | out of date |
| lazy_static | ^1 | 1.5.0 | up to date |
| p256 | ^0.9 | 0.13.2 | out of date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
ed25519-dalek: Double Public Key Signing Function Oracle Attack on `ed25519-dalek`Versions of ed25519-dalek prior to v2.0 model private and public keys as
separate types which can be assembled into a Keypair, and also provide APIs
for serializing and deserializing 64-byte private/public keypairs.
Such APIs and serializations are inherently unsafe as the public key is one of
the inputs used in the deterministic computation of the S part of the signature,
but not in the R value. An adversary could somehow use the signing function as
an oracle that allows arbitrary public keys as input can obtain two signatures
for the same message sharing the same R and only differ on the S part.
Unfortunately, when this happens, one can easily extract the private key.
Revised public APIs in v2.0 of ed25519-dalek do NOT allow a decoupled
private/public keypair as signing input, except as part of specially labeled
"hazmat" APIs which are clearly labeled as being dangerous if misused.