Amazon Linux 2 Security Advisory: ALAS-2020-1456
Advisory Release Date: 2020-07-14 02:39 Pacific
Advisory Updated Date: 2020-07-17 00:45 Pacific
In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s). (CVE-2019-1563)
Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s). (CVE-2019-1547)
OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). (CVE-2019-1549)
Affected Packages:
openssl11
Note:
This advisory is applicable to Amazon Linux 2 (AL2) Core repository. Visit this FAQ section for the difference between AL2 Core and AL2 Extras advisories.
Issue Correction:
Run yum update openssl11 to update your system.
aarch64:
openssl11-1.1.1c-15.amzn2.0.1.aarch64
openssl11-libs-1.1.1c-15.amzn2.0.1.aarch64
openssl11-devel-1.1.1c-15.amzn2.0.1.aarch64
openssl11-static-1.1.1c-15.amzn2.0.1.aarch64
openssl11-debuginfo-1.1.1c-15.amzn2.0.1.aarch64
i686:
openssl11-1.1.1c-15.amzn2.0.1.i686
openssl11-libs-1.1.1c-15.amzn2.0.1.i686
openssl11-devel-1.1.1c-15.amzn2.0.1.i686
openssl11-static-1.1.1c-15.amzn2.0.1.i686
openssl11-debuginfo-1.1.1c-15.amzn2.0.1.i686
src:
openssl11-1.1.1c-15.amzn2.0.1.src
x86_64:
openssl11-1.1.1c-15.amzn2.0.1.x86_64
openssl11-libs-1.1.1c-15.amzn2.0.1.x86_64
openssl11-devel-1.1.1c-15.amzn2.0.1.x86_64
openssl11-static-1.1.1c-15.amzn2.0.1.x86_64
openssl11-debuginfo-1.1.1c-15.amzn2.0.1.x86_64