Release Date: | 2019-02-27 |
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).
See more information about CVE-2019-1559 from MITRE CVE dictionary and NIST NVD
NOTE: The following CVSS v3.0 metrics and score provided are preliminary and subject to review.
Base Score: | 5.9 | Base Metrics: | AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Access Vector: | Network | Attack Complexity: | High |
Privileges Required: | None | User Interaction: | None |
Scope: | Unchanged | Confidentiality Impact: | High |
Integrity Impact: | None | Availability Impact: | None |
Platform | Errata | Release Date |
Oracle Linux version 6 (openssl) | ELSA-2019-2471 | 2019-08-14 |
Oracle Linux version 7 (openssl) | ELSA-2019-2304 | 2019-08-13 |
Oracle VM version 3.3 (openssl) | OVMSA-2019-0040 | 2019-08-15 |
Oracle VM version 3.4 (openssl) | OVMSA-2019-0040 | 2019-08-15 |
This page is generated automatically and has not been checked for errors or omissions. For clarification or corrections please contact the Oracle Linux ULN team