First published: Tue Dec 02 2003(Updated: )
GnuPG (GPG) 1.0.2, and other versions up to 1.2.3, creates ElGamal type 20 (sign+encrypt) keys using the same key component for encryption as for signing, which allows attackers to determine the private key from a signature.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
GnuPG | =1.0.2 | |
GnuPG | =1.0.3 | |
GnuPG | =1.0.3b | |
GnuPG | =1.0.4 | |
GnuPG | =1.0.5 | |
GnuPG | =1.0.6 | |
GnuPG | =1.0.7 | |
GnuPG | =1.2 | |
GnuPG | =1.2.1 | |
GnuPG | =1.2.2 | |
GnuPG | =1.2.2-rc1 | |
GnuPG | =1.2.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2003-0971 has a high severity as it allows attackers to deduce the private key from a signature.
The fix for CVE-2003-0971 is to upgrade GnuPG to version 1.2.4 or later.
CVE-2003-0971 affects GnuPG versions 1.0.2 through 1.2.3.
CVE-2003-0971 affects ElGamal type 20 keys which are used for signing and encrypting.
CVE-2003-0971 requires local access, making remote exploitation unlikely.