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

> Integer overflow in AVG Anti-Virus parsing of EXE files allows remote attackers to cause denial of service or execute arbitrary code.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qvpm-p6f4-j583

## What is CVE-2006-5940?

CVE-2006-5940 is a critical vulnerability in n/a, published on 16 Nov 2006. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official description

Unspecified vulnerability in Grisoft AVG Anti-Virus before 7.1.407 has unknown impact and remote attack vectors related to "Integer Issues" and parsing of .EXE files.

Weakness: CWE-189

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

It affects 1 product.


Products: Grisoft Avg Antivirus.

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

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

## Is CVE-2006-5940 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5938](https://insights.sbomify.com/CVE-2006-5938/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-5939](https://insights.sbomify.com/CVE-2006-5939/): Denial of service in n/a (high 7.8)
- [CVE-2006-5937](https://insights.sbomify.com/CVE-2006-5937/): Integer overflow in n/a (high 7.5)
- [CVE-2007-3777](https://insights.sbomify.com/CVE-2007-3777/): Privilege escalation in n/a (high 7.2)
- [CVE-2005-3371](https://insights.sbomify.com/CVE-2005-3371/): Security feature bypass in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5940 is a critical vulnerability in n/a, published on 16 Nov 2006. It can be exploited over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-5940 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-5940/ (Markdown: https://insights.sbomify.com/CVE-2006-5940/index.md)
```

## Sources

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

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