Summary
Package updates are available for Amazon Linux 2 that fix the following vulnerabilities: CVE-2019-1559: If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is received with an invalid MAC. If the application then behaves differently based on that in a way that is detectable to the remote peer, then this amounts to a padding oracle that could be used to decrypt data. In order for this to be exploitable "non-stitched" ciphersuites must be in use. Stitched ciphersuites are optimised implementations of certain commonly used ciphersuites. Also the application must call SSL_shutdown() twice even if a protocol error has occurred (applications should not do this but some do anyway). Fixed in OpenSSL 1.0.2r (Affected 1.0.2-1.0.2q). 1683804: CVE-2019-1559 openssl: 0-byte record padding oracle CVE-2018-5407: A microprocessor side-channel vulnerability was found on SMT (e.g, Hyper-Threading) architectures. An attacker running a malicious process on the same core of the processor as the victim process can extract certain secret information. 1645695: CVE-2018-5407 openssl: Side-channel vulnerability on SMT/Hyper-Threading architectures (PortSmash)
Fixed packages 6
| Release | Package | Fixed in |
|---|---|---|
| Amazon Linux · 2 | openssl | 1:1.0.2k-16.amzn2.1.1 |
| Amazon Linux · 2 | openssl-debuginfo | 1:1.0.2k-16.amzn2.1.1 |
| Amazon Linux · 2 | openssl-devel | 1:1.0.2k-16.amzn2.1.1 |
| Amazon Linux · 2 | openssl-libs | 1:1.0.2k-16.amzn2.1.1 |
| Amazon Linux · 2 | openssl-perl | 1:1.0.2k-16.amzn2.1.1 |
| Amazon Linux · 2 | openssl-static | 1:1.0.2k-16.amzn2.1.1 |
Vulnerabilities 2
-
Unscored —CVE-2018-5407 Public exploit
Simultaneous Multi-threading (SMT) in processors can enable local users to exploit software vulnerable to timing attack…
-
Unscored —CVE-2019-1559 EPSS 17%
0-byte record padding oracle
If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding …