dbcve.org
ClamavApplication · Clam Anti Virus

CVE-2008-1100

HIGH · 10.0 CVSS v2.0 Published 2008-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Buffer overflow in the cli_scanpe function in libclamav (libclamav/pe.c) for ClamAV 0.92 and 0.92.1 allows remote attackers to execute arbitrary code via a crafted Upack PE file.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Buffer overflow vulnerability in ClamAV's cli_scanpe function (libclamav/pe.c) allows remote code execution when scanning crafted Upack-packed PE executables. The vulnerability affects versions 0.92 and 0.92.1 specifically.

MitigationUpgrade ClamAV to version 0.92.2 or later which contains the fix for this buffer overflow. Until patched, avoid scanning untrusted PE files with affected versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ClamavApplication
Affected:= 0.92= 0.92.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed ClamAV version
    Run 'clamscan --version' or 'clamd --version' to retrieve the exact version number of your ClamAV installation
    Affected if The version displayed is exactly 0.92 or 0.92.1
  2. Verify PE scanning is enabled
    Confirm that ClamAV is configured to scan PE executable files. This is typically enabled by default in clamd.conf via 'ScanPE yes' or in clamscan via default behavior
    Affected if PE scanning is enabled (the default state for most ClamAV deployments)
  3. Confirm the vulnerable library file exists
    Verify that libclamav/pe.c was compiled into your installation by checking for the presence of the ClamAV library files in your system (typically in /usr/lib/clamav or similar path)
    Affected if The ClamAV library files are present and the version matches 0.92 or 0.92.1

You are affected if your installed ClamAV version is exactly 0.92 or 0.92.1 and PE file scanning is enabled, which is the default configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ClamAV to version 0.92.2 or later which contains the fix for this buffer overflow. Until patched, avoid scanning untrusted PE files with affected versions.

Recommended fix High confidence

ClamAV 0.92.2 or later (e.g., 0.93, 0.94)

  1. 1. Backup your current ClamAV configuration and database files.
  2. 2. Remove the currently installed ClamAV version (0.92 or 0.92.1).
  3. 3. Download ClamAV 0.92.2 or a later stable release from the official ClamAV website or your distribution's package repository.
  4. 4. Install the new ClamAV version using your system's package manager or by compiling from source.
  5. 5. Update the ClamAV signature database using 'freshclam'.
  6. 6. Verify the installation by running 'clamd --version' to confirm the new version is installed.
Caveat Minor: Review clamd.conf and freshclam.conf for any deprecated options between 0.92.x and newer versions; signature database format may require refresh

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Clamav Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-1100 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-1100 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data