CVE-2007-6596 json
ClamAV 0.92 does not recognize Base64 UUEncoded archives, which allows remote attackers to bypass the scanner via a Base64-UUEncoded file.
published 2007-12-31 18 y ago modified 2026-06-16 4 mo ago also EUVD-2007-6562
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
ClamAV 0.92 does not recognize Base64 UUEncoded archives, which allows remote attackers to bypass the scanner via a Base64-UUEncoded file.
Patch / fix
- clamav Debian 14, Debian 13, Debian 12 0.92.1~dfsg-1
debian advisories DEBIAN-CVE-2007-6596
- clamav openSUSE Tumbleweed 0.103.3-1.4
opensuse advisories openSUSE-SU-2024:10685-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2007-6596 updated
clamav does not recognize Base64-UUEncoded files
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.33% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
lists.opensuse.org
/opensuse-security-announce/2008-04/msg00009.html
vendor-advisory
-
securityreason.com
/securityalert/3501
third-party-advisory
-
secunia.com
/advisories/29891
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/39337
vdb-entry
-
securityfocus.com
/bid/27064
vdb-entry
-
securitytracker.com
/id?1019148
vdb-entry
-
securityfocus.com
/archive/1/485631/100/0/threaded
mailing-list
Sources
- CVE List CVE-2007-6596
- NVD CVE-2007-6596
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.