Use of a Broken or Risky Cryptographic Algorithm Affecting openssl-libs package, versions <1:1.0.2k-19.amzn2.0.3


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
3.14% (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 Learn

Learn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-AMZN2-OPENSSLLIBS-1678866
  • published27 Sept 2021
  • disclosed10 Sept 2019

Introduced: 10 Sep 2019

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

How to fix?

Upgrade Amazon-Linux:2 openssl-libs to version 1:1.0.2k-19.amzn2.0.3 or higher.
This issue was patched in ALAS2-2020-1406.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl-libs package and not the openssl-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2 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