This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate jwt-next

Dependencies

(14 total, 1 outdated, 1 insecure, 1 possibly insecure)

CrateRequiredLatestStatus
 base64^0.210.22.1out of date
 crypto-common^0.10.1.6up to date
 digest^0.100.10.7up to date
 ecdsa^0.160.16.9up to date
 hmac^0.120.12.1up to date
 openssl ⚠️^0.100.10.73maybe insecure
 p256^0.130.13.2up to date
 p384^0.130.13.1up to date
 pem^3.03.0.5up to date
 rsa ⚠️^0.90.9.8insecure
 serde^1.01.0.219up to date
 serde_json^1.01.0.140up to date
 sha2^0.100.10.9up to date
 signature^2.22.2.0up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 doc-comment^0.30.3.3up to date

Security Vulnerabilities

rsa: Marvin Attack: potential key recovery through timing sidechannels

RUSTSEC-2023-0071

Impact

Due 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.

Patches

No patch is yet available, however work is underway to migrate to a fully constant-time implementation.

Workarounds

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.

References

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.

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.