|
GnuPG "gpgv" Signature Verification Security Issue
|
|
Secunia Advisory:
|
SA18845
|
|
|
Release Date:
|
2006-02-15
|
|
Last Update:
|
2006-02-17
|
|
Popularity:
|
11,326 views
|
|
|
Critical:
|
Less critical
|
|
Impact:
|
Security Bypass
|
|
Where:
|
From remote
|
|
Solution Status:
|
Vendor Patch
|
|
| Software: | GnuPG / gpg 1.0.x
GnuPG / gpg 1.2.x
GnuPG / gpg 1.3.x
GnuPG / gpg 1.4.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 security issue has been reported in GnuPG, which potentially can be exploited by malicious people to bypass certain security restrictions.
The security issue is caused due to "gpgv" exiting with a return code of 0 even if the detached signature file did not carry any signature. This may result in certain scripts that use "gpgv" to conclude that the signature is correctly verified.
Successful exploitation requires that "gpgv" or "gpg --verify" is used from a script that determines whether the file signature is correctly verified based on the return code.
The security issue has been reported in versions prior to 1.4.2.1.
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.
|
