cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.
References
Link | Resource |
---|---|
https://lists.gnupg.org/pipermail/gcrypt-devel/2018-February/004394.html | Issue Tracking Third Party Advisory |
https://github.com/weikengchen/attack-on-libgcrypt-elgamal/wiki | Exploit Third Party Advisory |
https://github.com/weikengchen/attack-on-libgcrypt-elgamal | Third Party Advisory |
https://www.oracle.com/security-alerts/cpujan2020.html |
Configurations
Information
Published : 2018-02-07 15:29
Updated : 2020-01-15 12:15
NVD link : CVE-2018-6829
Mitre link : CVE-2018-6829
JSON object : View
CWE
CWE-327
Use of a Broken or Risky Cryptographic Algorithm
Products Affected
gnupg
- libgcrypt