dbcve.org
ClamavApplication · Clam Anti Virus

CVE-2007-6596

MEDIUM · 5.0 CVSS v2.0 Published 2007-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
ClamAV 0.92 does not recognize Base64 UUEncoded archives, which allows remote attackers to bypass the scanner via a Base64-UUEncoded 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

ClamAV version 0.92 lacks the capability to detect and unpack Base64 UUEncoded archives during scanning, allowing malicious files encoded in these formats to bypass antivirus detection. Attackers can embed malware within Base64 or UUEncoded containers that ClamAV 0.92 will not inspect.

MitigationUpgrade ClamAV to a version newer than 0.92 that includes support for Base64 and UUEncoded archive parsing, and ensure regular signature database updates are applied.

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

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
Partial
Integrity
None
Availability
None

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

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. Identify installed ClamAV version
    Run 'clamd --version' or 'freshclam --version' to display the ClamAV engine version
    Affected if The version displayed is exactly 0.92
  2. Confirm version matches CVE scope
    Verify that the installed version is exactly 0.92 with no additional subversions or patches listed
    Affected if The version is precisely 0.92 (not 0.92.1, 0.91, or later versions)
  3. Verify archive scanning is active
    Check clamd.conf for 'ArchiveScan' or 'ScanArchive' directives, or test with a sample archive scan to confirm archives are being examined
    Affected if ClamAV is configured to scan archives and the version is 0.92
  4. Check for Base64/UUEncoded detection capability
    Attempt to scan a Base64 or UUEncoded file containing a known test signature to see if ClamAV detects the embedded content
    Affected if ClamAV 0.92 fails to detect malware embedded in Base64 or UUEncoded archives

You are affected if ClamAV version 0.92 is installed and you rely on it to scan for malware within Base64 or UUEncoded encoded attachments or archives.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ClamAV to a version newer than 0.92 that includes support for Base64 and UUEncoded archive parsing, and ensure regular signature database updates are applied.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-6596 — 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-2007-6596 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