|
GnuPG ElGamal Signing Weakness Expose Private Key
|
|
Secunia Advisory:
|
SA10304
|
|
|
Release Date:
|
2003-11-27
|
|
Last Update:
|
2003-12-29
|
|
Popularity:
|
12,360 views
|
|
|
Critical:
|
Moderately critical
|
|
Impact:
|
Spoofing
Exposure of sensitive information
|
|
Where:
|
From remote
|
|
Solution Status:
|
Vendor Patch
|
|
| Software: | GnuPG / gpg 1.0.x
GnuPG / gpg 1.2.x
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
A weakness has been identified in the handling of ElGamal keys in GnuPG, which exposes the private key.
The problem is a that certain versions of GnuPG creates ElGamal sign+encrypt keys (type 20) in a cryptographically weak way. This can be exploited to derive the private key.
In an advisory from the developers of GnuPG, it is stated that all ElGamal type 20 keys should be considered compromised.
This affects ElGamal type 20 keys generated with GnuPG 1.0.2 to 1.2.3.
ElGamal encrypt-only keys (type 16) are not affected.
Further details are available in the original advisory.
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
