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.
crypto-primes(6 total, 1 outdated, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| crypto-bigint | ^0.6.1 | 0.6.1 | up to date |
| glass_pumpkin | ^1 | 1.7.0 | up to date |
| openssl ⚠️ | ^0.10.39 | 0.10.72 | maybe insecure |
| rand_core | ^0.6.4 | 0.9.3 | out of date |
| rayon | ^1 | 1.10.0 | up to date |
| rug | ^1.26 | 1.27.0 | up to date |
(9 total, 2 outdated)
| Crate | Required | Latest | Status |
|---|---|---|---|
| criterion | ^0.5 | 0.5.1 | up to date |
| crypto-bigint | ^0.6.1 | 0.6.1 | up to date |
| num-bigint | ^0.4 | 0.4.6 | up to date |
| num-integer | ^0.1 | 0.1.46 | up to date |
| num-modular | ^0.5 | 0.6.1 | out of date |
| num-prime | ^0.4.3 | 0.4.4 | up to date |
| num_cpus | ^1.16 | 1.16.0 | up to date |
| proptest | ^1 | 1.6.0 | up to date |
| rand_chacha | ^0.3 | 0.9.0 | out of date |
openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`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.