# CVE-2006-0455: Security feature bypass in n/a

> GnuPG returns a success exit code for unsigned files during unattended verification, allowing attackers to bypass signature checks.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-978-1, GHSA-575c-cp7m-ghgh

## What is CVE-2006-0455?

CVE-2006-0455 is a medium-severity vulnerability in n/a, published on 15 Feb 2006. 

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

## Which versions are affected by CVE-2006-0455?

It affects 1 product.


Products: Gnu Privacy Guard.

## How do I fix CVE-2006-0455?

Upgrade to a fixed version.

## Is CVE-2006-0455 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0455 exists.

Public exploit code:

- GnuPG 1.x - Detached Signature Verification Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6235](https://insights.sbomify.com/CVE-2006-6235/): Use after free in n/a (critical 10.0)
- [CVE-2003-0255](https://insights.sbomify.com/CVE-2003-0255/): Security feature bypass in n/a (critical 10.0)
- [CVE-2003-0978](https://insights.sbomify.com/CVE-2003-0978/): Memory corruption in n/a (high 7.5)
- [CVE-2001-0522](https://insights.sbomify.com/CVE-2001-0522/): Memory corruption in n/a (high 7.5)
- [CVE-2000-0974](https://insights.sbomify.com/CVE-2000-0974/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0455 and fix it if it is affected.

What it is: CVE-2006-0455 is a medium-severity vulnerability in n/a, published on 15 Feb 2006. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0455 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-0455/ (Markdown: https://insights.sbomify.com/CVE-2006-0455/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-0455
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-0455
- OSV: https://osv.dev/vulnerability/CVE-2006-0455

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-0455/
Summaries are generated and may contain mistakes; the official description above is the record.