Open github-actions[bot] opened 11 months ago
PSA for users: This attack is due to variable time operations during encryption and decryption.
We do not:
rsa
crate for anything but generating keysKeeping this open anyway.
Sidenote: PKCS#1 v1.5 has been deemed insecure for a long while now (around 25 years)
Muted the advisory. Remember to remove it when the rsa
crate got its constant-time impl
rsa
0.9.5
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.
See advisory page for additional details.