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

Crate jwt-simple

Dependencies

(19 total, 7 outdated, 1 insecure)

CrateRequiredLatestStatus
 anyhow^1.0.751.0.104up to date
 binstring^0.1.10.1.8up to date
 ciborium^0.2.10.2.2up to date
 coarsetime^0.1.310.1.38up to date
 ct-codecs^1.1.11.1.8up to date
 ed25519-compact^2.0.42.6.0up to date
 hmac-sha1-compact^1.1.41.1.8up to date
 hmac-sha256^1.1.71.1.15up to date
 hmac-sha512^1.1.51.1.13up to date
 k256^0.13.10.14.0out of date
 p256^0.13.20.14.0out of date
 p384^0.13.00.14.0out of date
 rand^0.8.50.10.3out of date
 rsa ⚠️^0.7.20.9.10insecure
 serde^1.0.1901.0.229up to date
 serde_json^1.0.1081.0.151up to date
 spki^0.6.00.8.0out of date
 thiserror^1.0.502.0.21out of date
 zeroize^1.6.01.9.0up to date

Dev dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 benchmark-simple^0.1.80.2.0out of 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. The crypto-bigint migration (RustCrypto/RSA#394) did not close this. Tracking is RustCrypto/RSA#626 (padding still not constant-time). Implicit rejection work is in RustCrypto/RSA#680; default-path blinding is in RustCrypto/RSA#702.

Still affected as of 2026-09-12: rsa 0.9.10 (latest stable) and rsa 0.10.0-rc.18 (latest). patched = [] is intentional.

Workarounds

Avoid using the rsa crate in settings where attackers can observe timing, for example over the network. 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.