# CVE-2007-6745: Denial of service in clamav

> A floating point exception in ClamAV's OLE2 scanner allows attackers to cause a denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Nov 2019
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-6745, GHSA-x9fv-8cwx-6m58

## What is CVE-2007-6745?

CVE-2007-6745 is a critical denial of service vulnerability in Clamav Clamav, published on 7 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

clamav 0.91.2 suffers from a floating point exception when using ScanOLE2.

## Which versions are affected by CVE-2007-6745?

It affects 2 products.


Products: Clamav Clamav, Debian Debian Linux.

## How do I fix CVE-2007-6745?

Upgrade to a fixed version.

## Is CVE-2007-6745 being exploited?

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

## Other vulnerabilities in Clamav Clamav

- [CVE-2010-0098](https://insights.sbomify.com/CVE-2010-0098/): Security feature bypass in n/a (critical 10.0)
- [CVE-2009-1372](https://insights.sbomify.com/CVE-2009-1372/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-3914](https://insights.sbomify.com/CVE-2008-3914/): Denial of service in n/a (critical 10.0)
- [CVE-2008-0728](https://insights.sbomify.com/CVE-2008-0728/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-1615](https://insights.sbomify.com/CVE-2006-1615/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-6745 and fix it if it is affected.

What it is: CVE-2007-6745 is a critical denial of service vulnerability in Clamav Clamav, published on 7 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-6745 in the wild and no public exploit code.

Affected product: Clamav Clamav. 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-2007-6745/ (Markdown: https://insights.sbomify.com/CVE-2007-6745/index.md)
```

## Sources

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

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