Количество 54
Количество 54
ELSA-2019-2304
ELSA-2019-2304: openssl security and bug fix update (MODERATE)
SUSE-SU-2019:1553-1
Security update for openssl
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).
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).
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).
CVE-2019-1559
If an application encounters a fatal protocol error and then calls SSL ...
CVE-2018-0734
The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).
CVE-2018-0734
The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).
CVE-2018-0734
The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).
CVE-2018-0734
CVE-2018-0734
The OpenSSL DSA signature algorithm has been shown to be vulnerable to ...
openSUSE-SU-2019:1637-1
Security update for compat-openssl098
openSUSE-SU-2019:1432-1
Security update for openssl-1_0_0
openSUSE-SU-2019:1175-1
Security update for openssl
openSUSE-SU-2019:1105-1
Security update for openssl-1_0_0
SUSE-SU-2019:1608-1
Security update for compat-openssl098
SUSE-SU-2019:14092-1
Security update for openssl
SUSE-SU-2019:14091-1
Security update for openssl1
SUSE-SU-2019:1362-1
Security update for openssl
SUSE-SU-2019:0803-1
Security update for openssl
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
| ELSA-2019-2304 ELSA-2019-2304: openssl security and bug fix update (MODERATE) | почти 6 лет назад | ||
 | SUSE-SU-2019:1553-1 Security update for openssl | около 6 лет назад | ||
 | 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). | CVSS3: 5.9 | 4% Низкий | больше 6 лет назад |
 | 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). | CVSS3: 5.9 | 4% Низкий | больше 6 лет назад |
 | 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). | CVSS3: 5.9 | 4% Низкий | больше 6 лет назад |
| CVE-2019-1559 If an application encounters a fatal protocol error and then calls SSL ... | CVSS3: 5.9 | 4% Низкий | больше 6 лет назад |
| CVE-2018-0734 The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p). | CVSS3: 5.9 | 6% Низкий | больше 6 лет назад |
| CVE-2018-0734 The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p). | CVSS3: 5.1 | 6% Низкий | больше 6 лет назад |
| CVE-2018-0734 The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p). | CVSS3: 5.9 | 6% Низкий | больше 6 лет назад |
 | CVSS3: 5.9 | 6% Низкий | около 4 лет назад | |
| CVE-2018-0734 The OpenSSL DSA signature algorithm has been shown to be vulnerable to ... | CVSS3: 5.9 | 6% Низкий | больше 6 лет назад |
| openSUSE-SU-2019:1637-1 Security update for compat-openssl098 | 4% Низкий | почти 6 лет назад | |
| openSUSE-SU-2019:1432-1 Security update for openssl-1_0_0 | 4% Низкий | около 6 лет назад | |
| openSUSE-SU-2019:1175-1 Security update for openssl | 4% Низкий | около 6 лет назад | |
| openSUSE-SU-2019:1105-1 Security update for openssl-1_0_0 | 4% Низкий | около 6 лет назад | |
| SUSE-SU-2019:1608-1 Security update for compat-openssl098 | 4% Низкий | почти 6 лет назад | |
| SUSE-SU-2019:14092-1 Security update for openssl | 4% Низкий | почти 6 лет назад | |
| SUSE-SU-2019:14091-1 Security update for openssl1 | 4% Низкий | около 6 лет назад | |
| SUSE-SU-2019:1362-1 Security update for openssl | 4% Низкий | около 6 лет назад | |
| SUSE-SU-2019:0803-1 Security update for openssl | 4% Низкий | около 6 лет назад |
Уязвимостей на страницу