Deps.rs

jwt-simple 0.11.9

[![dependency status](https://deps.rs/crate/jwt-simple/0.11.9/status.svg)](https://deps.rs/crate/jwt-simple/0.11.9)

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

Crate jwt-simple

Dependencies

(19 total, 2 outdated, 1 insecure)

CrateRequiredLatestStatus
 anyhow^1.0.751.0.82up to date
 binstring^0.1.10.1.1up to date
 ciborium^0.2.10.2.2up to date
 coarsetime^0.1.310.1.34up to date
 ct-codecs^1.1.11.1.1up to date
 ed25519-compact^2.0.42.1.1up to date
 hmac-sha1-compact^1.1.41.1.4up to date
 hmac-sha256^1.1.71.1.7up to date
 hmac-sha512^1.1.51.1.5up to date
 k256^0.13.10.13.3up to date
 p256^0.13.20.13.2up to date
 p384^0.13.00.13.0up to date
 rand^0.8.50.8.5up to date
 rsa ⚠️^0.7.20.9.6insecure
 serde^1.0.1901.0.200up to date
 serde_json^1.0.1081.0.116up to date
 spki^0.6.00.7.3out of date
 thiserror^1.0.501.0.59up to date
 zeroize^1.6.01.7.0up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 benchmark-simple^0.1.80.1.9up 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.