CVE-2006-0455: Medium severity GNU Privacy Guard vulnerability

Published Feb 15, 2006
·
Updated

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".

Affected Software

23 affected components
GNU Privacy Guard=1.0
GNU Privacy Guard=1.0.1
GNU Privacy Guard=1.0.2
GNU Privacy Guard=1.0.3
GNU Privacy Guard=1.0.3b
GNU Privacy Guard=1.0.4
GNU Privacy Guard=1.0.5
GNU Privacy Guard=1.0.6
GNU Privacy Guard=1.0.7
GNU Privacy Guard=1.2
GNU Privacy Guard=1.2.1
GNU Privacy Guard=1.2.2
GNU Privacy Guard=1.2.2-rc1
GNU Privacy Guard=1.2.3
GNU Privacy Guard=1.2.4
GNU Privacy Guard=1.2.5
GNU Privacy Guard=1.2.6
GNU Privacy Guard=1.2.7
GNU Privacy Guard=1.3.3
GNU Privacy Guard=1.3.4
GNU Privacy Guard=1.4
GNU Privacy Guard=1.4.1
GNU Privacy Guard=1.4.2

Event History

Feb 15, 2006
CVE Published
10:06 PM
Feb 16, 2006
CVE Published
via MITRE·03:00 AM
Data Sourced
via MITRE·03:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2006-0455?

CVE-2006-0455 is considered a medium severity vulnerability due to its potential to mislead programs into assuming a successful signature verification.

2

How do I fix CVE-2006-0455?

To fix CVE-2006-0455, upgrade to GnuPG version 1.4.2.1 or later, where this issue has been resolved.

3

What software is affected by CVE-2006-0455?

CVE-2006-0455 affects GnuPG versions prior to 1.4.2.1, specifically versions 1.0 to 1.4.1.

4

How does CVE-2006-0455 impact digital signature verification?

CVE-2006-0455 can cause gpgv to return a success exit code even when a detached signature file lacks a valid signature, leading to false confidence in security.

5

Are there workaround solutions for CVE-2006-0455?

While upgrading GnuPG is the best solution for CVE-2006-0455, using additional verification processes outside of gpgv could serve as a temporary workaround.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203