Information Exposure Affecting libopenssl1_0_0 package, versions <1.0.2p-3.14.2


Severity

Recommended
low

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
1.4% (87th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES150-LIBOPENSSL100-2756860
  • published14 Apr 2022
  • disclosed12 Mar 2019

Introduced: 12 Mar 2019

CVE-2019-1559  (opens in a new tab)
CWE-203  (opens in a new tab)

How to fix?

Upgrade SLES:15.0 libopenssl1_0_0 to version 1.0.2p-3.14.2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libopenssl1_0_0 package and not the libopenssl1_0_0 package as distributed by SLES. See How to fix? for SLES:15.0 relevant fixed versions and status.

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).

References

CVSS Scores

version 3.1