Upstream information
Description
gpgv in GnuPG before 1.4.2.1, when using unattended signature verification, returns a 0 exit code in certain cases even when the detached signature file does not carry a signature, which could cause programs that use gpgv to assume that the signature verification has succeeded. Note: this also occurs when running the equivalent command "gpg --verify".SUSE information
Overall state of this security issue: Resolved
This issue is currently rated as having important severity.
| National Vulnerability Database | |
|---|---|
| Base Score | 4.6 |
| Vector | AV:L/AC:L/Au:N/C:P/I:P/A:P |
| Access Vector | Local |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | Partial |
| Availability Impact | Partial |
SUSE Security Advisories:
- SUSE-SA:2006:009, published Mon, 20 Feb 2006 18:00:00 +0000
- SUSE-SA:2006:013, published Wed, 01 Mar 2006 11:00:00 +0000
- SUSE-SR:2006:005, published Fri, 03 Mar 2006 15:00:00 +0000
List of released packages
| Product(s) | Fixed package version(s) | References |
|---|---|---|
| SUSE Linux Micro 6.0 |
| Patchnames: SUSE Linux Micro 6.0 GA gpg2-2.4.4-1.2 |
| SUSE Linux Micro 6.1 |
| Patchnames: SUSE Linux Micro 6.1 GA gpg2-2.4.4-slfo.1.1_1.2 |
| openSUSE Tumbleweed |
| Patchnames: openSUSE-Tumbleweed-2024-10815 |
SUSE Timeline for this CVE
CVE page created: Fri Jun 28 01:31:35 2013CVE page last modified: Tue Dec 17 16:12:54 2024