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

Cache timing vulnerability in RSA Key Generation (CVE-2018-0737) #208

Closed
anonimal opened this issue Apr 17, 2018 · 4 comments
Closed

Cache timing vulnerability in RSA Key Generation (CVE-2018-0737) #208

anonimal opened this issue Apr 17, 2018 · 4 comments

Comments

@anonimal
Copy link
Contributor

This is for our static release builds, regarding our usage of libunbound (RSA/SHA1 required for DNSSEC). RSA also needed for epee(?), and more(?) (? = can @moneromooo-monero or @hyc or others confirm?):

https://www.openssl.org/news/secadv/20180416.txt

Due to the low severity of this issue we are not issuing a new release of
OpenSSL 1.1.0 or 1.0.2 at this time. The fix will be included in OpenSSL 1.1.0i
and OpenSSL 1.0.2p when they become available.

If the next point release is not before they release 1.1.0i / 1.0.2p, then we should release a monero point release with those applicable versions once they are released.

@hyc
Copy link

hyc commented Apr 17, 2018

Only libunbound had any particular OpenSSL requirement.

@fluffypony
Copy link
Contributor

Yes - only needed for libunbound

@anonimal
Copy link
Contributor Author

anonimal commented Sep 8, 2018

1.1.0i was released August 14th. The static release binaries should be built against the latest version of openssl.

@anonimal
Copy link
Contributor Author

Should be resolved in the v0.13 series.

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

3 participants