Debian LinuxOperating system · Debian
CVE-2007-0899
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 · uneditedThere is a possible heap overflow in libclamav/fsg.c before 0.100.0.
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 confidenceA heap overflow vulnerability exists in libclamav/fsg.c in ClamAV versions prior to 0.100.0. This flaw in the file signature grouping parser allows remote code execution through specially crafted archive files scanned by the antivirus engine.
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
Debian LinuxOperating system
= 8.0= 9.0= 10.0< 0.100.0CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify ClamAV is installedRun `clamd --version` or `clamscan --version` to check if ClamAV is present on the systemAffected if ClamAV is not installed, so the vulnerability does not apply
-
Check installed ClamAV versionCompare the version output from step 1 against the affected range of versions prior to 0.100.0Affected if The installed version is less than 0.100.0 (e.g., 0.99.x, 0.98.x, etc.)
-
Confirm archive scanning is enabledInspect the ClamAV configuration file (typically /etc/clamd.conf or /etc/clamav/clamd.conf) for directives that enable archive scanning such as `ScanArchive` or similar archive-related optionsAffected if Archive scanning is enabled and the system scans archive files with ClamAV
-
Check for the vulnerable fsg moduleVerify the presence of the file signature grouping module (libclamav/fsg.c compiled library) in the ClamAV lib directory, typically found at /usr/lib/clamav or /usr/lib/x86_64-linux-gnu/clamavAffected if The fsg module exists in the ClamAV installation and is used during signature processing
A system is affected if ClamAV is installed with a version prior to 0.100.0 and archive scanning is enabled, allowing specially crafted archive files to trigger the heap overflow in libclamav/fsg.c during scans.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.100.0
Upgrade ClamAV to version 0.100.0 or later to patch the heap overflow in libclamav/fsg.c.
ClamAV 0.100.0 or later (Debian packages)
- Run 'apt-get update' to refresh package lists
- Run 'apt-get install clamav clamav-daemon' to upgrade ClamAV to the latest available version in your Debian repository
- Verify the installed version is 0.100.0 or later using 'clamd --version'
- If clamd is running, restart it with 'systemctl restart clamd' or 'service clamd restart'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0899 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-0899 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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