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


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
3.31% (92nd 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-SLES151-LIBOPENSSL100-2730729
  • published14 Apr 2022
  • disclosed4 Oct 2019

Introduced: 4 Oct 2019

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

How to fix?

Upgrade SLES:15.1 libopenssl1_0_0 to version 1.0.2p-3.22.1 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.1 relevant fixed versions and status.

In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, 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 info 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).

References

CVSS Scores

version 3.1