CVE-2018-6829
Last modified
CVE-2018-6829 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.81% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Gnupg | Libgcrypt | <= 1.8.2 |
References
- https://github.com/weikengchen/attack-on-libgcrypt-elgamalThird Party Advisory
- https://github.com/weikengchen/attack-on-libgcrypt-elgamal/wikiExploit, Third Party Advisory
- https://lists.gnupg.org/pipermail/gcrypt-devel/2018-February/004394.htmlIssue Tracking, Third Party Advisory
- https://github.com/weikengchen/attack-on-libgcrypt-elgamalThird Party Advisory
- https://github.com/weikengchen/attack-on-libgcrypt-elgamal/wikiExploit, Third Party Advisory
- https://lists.gnupg.org/pipermail/gcrypt-devel/2018-February/004394.htmlIssue Tracking, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-6829?
How severe is CVE-2018-6829?
How do I fix CVE-2018-6829?
Are you affected by CVE-2018-6829?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
