CVE-2018-6829: High severity gnupg Libgcrypt vulnerability
Published Feb 7, 2018
·Updated
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.
Affected Software
1 affected component
gnupg Libgcrypt<=1.8.2
Event History
Feb 7, 2018
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description
Data Sourced
via NVD·11:29 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the vulnerability ID for this vulnerability?
The vulnerability ID for this vulnerability is CVE-2018-6829.
2
What is the severity of CVE-2018-6829?
CVE-2018-6829 has a severity level of high (7.5).
3
How does CVE-2018-6829 impact the affected software?
CVE-2018-6829 allows attackers to obtain sensitive information by reading ciphertext data.
4
How can I fix the vulnerability in Libgcrypt?
To fix CVE-2018-6829, you should update Libgcrypt to version 1.8.3 or later.
5
Where can I find more information about CVE-2018-6829?
You can find more information about CVE-2018-6829 at the following references: [1] [2] [3]