This project contains known security vulnerabilities. Find detailed information at the bottom.
jwt-next(14 total, 1 outdated, 1 insecure, 1 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| base64 | ^0.21 | 0.22.1 | out of date |
| crypto-common | ^0.1 | 0.1.6 | up to date |
| digest | ^0.10 | 0.10.7 | up to date |
| ecdsa | ^0.16 | 0.16.9 | up to date |
| hmac | ^0.12 | 0.12.1 | up to date |
| openssl ⚠️ | ^0.10 | 0.10.64 | maybe insecure |
| p256 | ^0.13 | 0.13.2 | up to date |
| p384 | ^0.13 | 0.13.0 | up to date |
| pem | ^3.0 | 3.0.4 | up to date |
| rsa ⚠️ | ^0.9 | 0.9.6 | insecure |
| serde | ^1.0 | 1.0.202 | up to date |
| serde_json | ^1.0 | 1.0.117 | up to date |
| sha2 | ^0.10 | 0.10.8 | up to date |
| signature | ^2.2 | 2.2.0 | up to date |
(1 total, all up-to-date)
| Crate | Required | Latest | Status |
|---|---|---|---|
| doc-comment | ^0.3 | 0.3.3 | up to date |
openssl: `openssl` `X509VerifyParamRef::set_host` buffer over-readWhen this function was passed an empty string, openssl would attempt to call strlen on it, reading arbitrary memory until it reached a NUL byte.
rsa: Marvin Attack: potential key recovery through timing sidechannelsDue to a non-constant-time implementation, information about the private key is leaked through timing information which is observable over the network. An attacker may be able to use that information to recover the key.
No patch is yet available, however work is underway to migrate to a fully constant-time implementation.
The only currently available workaround is to avoid using the rsa crate in settings where attackers are able to observe timing information, e.g. local use on a non-compromised computer is fine.
This vulnerability was discovered as part of the "Marvin Attack", which revealed several implementations of RSA including OpenSSL had not properly mitigated timing sidechannel attacks.