Use of a Broken or Risky Cryptographic Algorithm Affecting libgcrypt20 package, versions <1.8.7-6
Threat Intelligence
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 ID SNYK-DEBIAN12-LIBGCRYPT20-1582896
- published 7 Sep 2021
- disclosed 6 Sep 2021
Introduced: 6 Sep 2021
CVE-2021-40528 Open this link in a new tabHow to fix?
Upgrade Debian:12 libgcrypt20 to version 1.8.7-6 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
The ElGamal implementation in Libgcrypt before 1.9.4 allows plaintext recovery because, during interaction between two cryptographic libraries, a certain dangerous combination of the prime defined by the receiver's public key, the generator defined by the receiver's public key, and the sender's ephemeral exponents can lead to a cross-configuration attack against OpenPGP.
References
- https://security-tracker.debian.org/tracker/CVE-2021-40528
- https://eprint.iacr.org/2021/923
- https://ibm.github.io/system-security-research-updates/2021/07/20/insecurity-elgamal-pt1
- https://ibm.github.io/system-security-research-updates/2021/09/06/insecurity-elgamal-pt2
- https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=3462280f2e23e16adf3ed5176e0f2413d8861320
- https://security.gentoo.org/glsa/202210-13
- https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git%3Ba=commit%3Bh=3462280f2e23e16adf3ed5176e0f2413d8861320