[arch-security] [ASA-201601-11] go: information leakage
rgacogne at archlinux.org
Sat Jan 16 15:43:26 UTC 2016
Arch Linux Security Advisory ASA-201601-11
Date : 2016-01-16
CVE-ID : CVE-2015-8618
Package : go
Type : information leakage
Remote : Yes
Link : https://wiki.archlinux.org/index.php/CVE
The package go before version 2:1.5.3-1 is vulnerable to information
Please note that Go programs doing RSA computations must be recompiled
with Go 1.5.3 in order to receive the fix. We are currently rebuilding
several Arch packages concerned by this issue.
Upgrade to 2:1.5.3-1.
# pacman -Syu "go>=2:1.5.3-1"
The problem has been fixed upstream in version 1.5.3.
This issue can affect RSA computations in crypto/rsa, which is used by
crypto/tls. TLS servers on 32-bit systems could plausibly leak their RSA
private key due to this issue. Other protocol implementations that
create many RSA signatures could also be impacted in the same way.
Specifically, incorrect results in one part of the RSA Chinese Remainder
computation can cause the result to be incorrect in such a way that it
leaks one of the primes. While RSA blinding should prevent an attacker
from crafting specific inputs that trigger the bug, on 32-bit systems
the bug can be expected to occur at random around one in 2^26 times.
Thus collecting around 64 million signatures (of known data) from an
affected server should be enough to extract the private key used.
On 64-bit systems, the frequency of the bug is so low (less than one in
2^50) that it would be very difficult to exploit. Nonetheless, everyone
is strongly encouraged to upgrade.
A remote unauthenticated attacker can extract a private RSA key by
passively collecting signatures.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 801 bytes
Desc: OpenPGP digital signature
More information about the arch-security