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

> Attackers can bypass signature verification in GnuPG by injecting unsigned data, allowing them to present tampered content as validly signed.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-993-2, GHSA-c5p7-4hq8-gm4c

## What is CVE-2006-0049?

CVE-2006-0049 is a medium-severity vulnerability in n/a, published on 13 Mar 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

gpg in GnuPG before 1.4.2.2 does not properly verify non-detached signatures, which allows attackers to inject unsigned data via a data packet that is not associated with a control packet, which causes the check for concatenated signatures to report that the signature is valid, a different vulnerability than CVE-2006-0455.

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

It affects 1 product.


Products: Gnu Privacy Guard.

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

Upgrade to a fixed version.

## Is CVE-2006-0049 being exploited?

There is no known exploitation of CVE-2006-0049 in the wild and no public exploit code.

## 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-0049 and fix it if it is affected.

What it is: CVE-2006-0049 is a medium-severity vulnerability in n/a, published on 13 Mar 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-0049 in the wild and no public exploit code.

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-0049/ (Markdown: https://insights.sbomify.com/CVE-2006-0049/index.md)
```

## Sources

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

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