# CVE-2006-6627: Integer overflow in n/a

> Remote attackers can execute arbitrary code via a crafted file due to an integer overflow in BitDefender's PE parser, requiring user interaction to open the file.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** No
- **Published:** 18 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3gfm-x3mg-hww2

## What is CVE-2006-6627?

CVE-2006-6627 is a critical vulnerability in n/a, published on 18 Dec 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

Integer overflow in the packed PE file parsing implementation in BitDefender products before 20060829, including Antivirus, Antivirus Plus, Internet Security, Mail Protection for Enterprises, and Online Scanner; and BitDefender products for Microsoft ISA Server and Exchange 5.5 through 2003; allows remote attackers to execute arbitrary code via a crafted file, which triggers a heap-based buffer overflow, aka the "cevakrnl.xmd vulnerability."

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

It affects 5 products.


Products: Softwin Bitdefender, Softwin Bitdefender Antivirus, Softwin Bitdefender Internet Security, Softwin Bitdefender Mail Protection, Softwin Bitdefender Online Scanner.

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

No fix has been published for CVE-2006-6627 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-6627 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-3154](https://insights.sbomify.com/CVE-2005-3154/): Other in n/a (high 7.5)
- [CVE-2004-1947](https://insights.sbomify.com/CVE-2004-1947/): Code injection in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6627 is a critical vulnerability in n/a, published on 18 Dec 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-6627 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-6627/ (Markdown: https://insights.sbomify.com/CVE-2006-6627/index.md)
```

## Sources

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

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