# CVE-2009-1371: The CLI_ISCONTAINED macro in libclamav/others.h in ClamAV before 0.95.1 allows remote attackers to cause a denial of service (application cr


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-1371, GHSA-93pj-83f5-xggg

## What is CVE-2009-1371?

CVE-2009-1371 is a medium-severity vulnerability in Clamav Clamav, published on 23 Apr 2009. 

### Official description

The CLI_ISCONTAINED macro in libclamav/others.h in ClamAV before 0.95.1 allows remote attackers to cause a denial of service (application crash) via a malformed file with UPack encoding.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2009-1371?

It affects 1 product.


Products: Clamav Clamav.

## How do I fix CVE-2009-1371?

Upgrade to a fixed version.

## Is CVE-2009-1371 being exploited?

There is no known exploitation of CVE-2009-1371 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-2009-1371 and fix it if it is affected.

What it is: CVE-2009-1371 is a medium-severity vulnerability in Clamav Clamav, published on 23 Apr 2009. 
Exploitation: There is no known exploitation of CVE-2009-1371 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-2009-1371/ (Markdown: https://insights.sbomify.com/CVE-2009-1371/index.md)
```

## Sources

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

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