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 osshkeys

Dependencies

(21 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 base64^0.21.00.22.0out of date
 byteorder^1.4.31.5.0up to date
 openssl ⚠️^0.10.300.10.64maybe insecure
 rand^0.8.50.8.5up to date
 ed25519-dalek ⚠️^2.0.0-rc.22.1.1maybe insecure
 zeroize^1.1.01.7.0up to date
 log^0.4.80.4.21up to date
 backtrace^0.3.460.3.71up to date
 pem^2.0.13.0.3out of date
 regex^1.8.31.10.4up to date
 digest^0.10.20.10.7up to date
 md-5^0.10.00.10.6up to date
 sha-1^0.10.00.10.1up to date
 sha2^0.10.10.10.8up to date
 bcrypt-pbkdf^0.10.00.10.0up to date
 cryptovec^0.6.10.6.1up to date
 cipher^0.4.00.4.4up to date
 cbc^0.1.00.1.2up to date
 ctr^0.9.00.9.2up to date
 aes^0.8.00.8.4up to date
 des^0.8.00.8.1up to date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 hex^0.4.00.4.3up to date
 hex-literal^0.4.10.4.1up to date
 cfg-if^1.0.01.0.0up to date

Security Vulnerabilities

ed25519-dalek: Double Public Key Signing Function Oracle Attack on `ed25519-dalek`

RUSTSEC-2022-0093

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.

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.