Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RUSTSEC-2023-0071: Marvin Attack: potential key recovery through timing sidechannels #157

Open
github-actions bot opened this issue Oct 5, 2024 · 3 comments

Comments

@github-actions
Copy link

github-actions bot commented Oct 5, 2024

Marvin Attack: potential key recovery through timing sidechannels

Details
Package rsa
Version 0.9.6
URL RustCrypto/RSA#19 (comment)
Date 2023-11-22

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.

@rustaceanrob
Copy link
Owner

From arti project dependencies

@oleonardolima
Copy link
Contributor

FWIW it's a known issue by Arti's team, and I also noticed that when adding MVP tor support on fedimint.

As the arti team mentions it should not be affected as it does not use any private-key operation with RSA, but still a vulnerability in RSA nonetheless (ref.: https://gitlab.torproject.org/tpo/core/arti/-/blob/main/maint/cargo_audit#L22-27).

@rustaceanrob
Copy link
Owner

Thanks for the details on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants