Use of a Broken or Risky Cryptographic Algorithm Affecting libgcrypt-devel package, versions <0:1.5.3-12.20.amzn1


Severity

Recommended
medium

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.19% (57th 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-AMZN201803-LIBGCRYPTDEVEL-2443145
  • published8 Apr 2022
  • disclosed8 Jun 2021

Introduced: 8 Jun 2021

CVE-2021-33560  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2018.03 libgcrypt-devel to version 0:1.5.3-12.20.amzn1 or higher.
This issue was patched in ALAS-2022-1578.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt-devel package and not the libgcrypt-devel package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel attack against mpi_powm, and the window size is not chosen appropriately. This, for example, affects use of ElGamal in OpenPGP.

CVSS Scores

version 3.1