Security Bulletin
Summary
Multiple Vulnerabilities CVE-2019-1547, CVE-2019-1549 and CVE-2019-1563 in openssl package
Vulnerability Details
CVEID: CVE-2019-1547
DESCRIPTION: Normally in OpenSSL, EC groups always have a cofactor that is used in side channel resistant code paths. However, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that an EC 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 exploit this vulnerability, an attacker would have to be able to time the creation of a large number of signatures where explicit parameters with no cofactor present are in use by an application using libcrypto. Note that 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).
CVSS Base score: 5.5
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/167020 for the current score.
CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N)
CVEID: CVE-2019-1549
DESCRIPTION: 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 used by default. 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 a state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly by 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).
CVSS Base score: 3.7
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/167021 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)
CVEID: CVE-2019-1563
DESCRIPTION: In situations where an attacker receives automated notification of the success or failure of a decryption attempt, an attacker can send a very large number of messages to be decrypted and then recover a CMS/PKCS7 transported encryption key or can decrypt any RSA encrypted message that was encrypted with the public RSA key by 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 information 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).
CVSS Base score: 3.7
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/167022 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)
DESCRIPTION: Normally in OpenSSL, EC groups always have a cofactor that is used in side channel resistant code paths. However, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that an EC 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 exploit this vulnerability, an attacker would have to be able to time the creation of a large number of signatures where explicit parameters with no cofactor present are in use by an application using libcrypto. Note that 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).
CVSS Base score: 5.5
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/167020 for the current score.
CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N)
CVEID: CVE-2019-1549
DESCRIPTION: 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 used by default. 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 a state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly by 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).
CVSS Base score: 3.7
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/167021 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)
CVEID: CVE-2019-1563
DESCRIPTION: In situations where an attacker receives automated notification of the success or failure of a decryption attempt, an attacker can send a very large number of messages to be decrypted and then recover a CMS/PKCS7 transported encryption key or can decrypt any RSA encrypted message that was encrypted with the public RSA key by 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 information 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).
CVSS Base score: 3.7
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/167022 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)
Affected Products and Versions
| Affected Product(s) | Version(s) |
| IBM PowerAI Vision | 1.1.3 |
| IBM PowerAI Vision | 1.1.4 |
Remediation/Fixes
Openssl has been upgraded in PowerAI Vision 1.1.5 to a level that addresses this vulnerability.
Workarounds and Mitigations
None
Get Notified about Future Security Bulletins
References
Off
Change History
17 Dec 2019: Initial Publication
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
Disclaimer
Review the IBM security bulletin disclaimer and definitions regarding your responsibilities for assessing potential impact of security vulnerabilities to your environment.
Document Location
Worldwide
[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSRU69","label":"IBM PowerAI Vision"},"Component":"openssl","Platform":[{"code":"PF043","label":"Red Hat"}],"Version":"1.1.4","Edition":"ALL","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
08 January 2020
UID
ibm11168564