ClamAV error: CL_EFORMAT: Bad format or broken data
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ClamAV |
Fix Released
|
Medium
|
|||
Hardy Backports |
Fix Released
|
High
|
Scott Kitterman | ||
Lucid Backports |
Fix Released
|
High
|
Scott Kitterman | ||
clamav (Debian) |
Fix Released
|
Unknown
|
|||
clamav (Ubuntu) |
Fix Released
|
High
|
Scott Kitterman | ||
Natty |
Fix Released
|
High
|
Steve Beattie | ||
Oneiric |
Fix Released
|
High
|
Steve Beattie | ||
Precise |
Fix Released
|
High
|
Steve Beattie | ||
Quantal |
Fix Released
|
High
|
Scott Kitterman |
Bug Description
[IMPACT]
* Scanning errors on some files of some important types like PDF, DOC, XLS, and tar.bz2.
* Can cause major disruption of mail servers and other applications
* Regression from previous releases
* Bug fix is upstream fix that will be included in the next clamav release.
[TESTCASE]
* sudo apt-get install clamav (if not already installed) and once the package is installed and signatures are downloaded you are ready to test.
* With an appropriate test file (the thunderbird bz2 file that is attached to the bug is one such file) run $ clamscan $FILENAME and you should get an error as described in the original bug.
* Install the updated packages from -proposed
* Run the test again and it should test OK (no error and no virus found).
[Regression Potential]
* Nil. Patch taken from upstream and given where the patch is in the code it would be very difficult to regress.
Original bug:
got this in my syslog after update of clamav dunno if its a bug or not
Jun 19 21:47:29 server dansguardian[]: ClamAV error: CL_EFORMAT: Bad format or broken data
Jun 19 21:47:29 server dansguardian[]: scanFile/Memory returned error: -1
update version
0.97.5
ubuntu 11.04
Changed in clamav (Ubuntu): | |
milestone: | none → ubuntu-12.10-beta-1 |
assignee: | nobody → Scott Kitterman (kitterman) |
importance: | Undecided → High |
Changed in clamav (Ubuntu Precise): | |
status: | New → Triaged |
Changed in clamav (Ubuntu Oneiric): | |
status: | New → Triaged |
Changed in clamav (Ubuntu Natty): | |
status: | New → Triaged |
Changed in lucid-backports: | |
status: | New → Triaged |
Changed in hardy-backports: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in lucid-backports: | |
importance: | Undecided → High |
Changed in clamav (Ubuntu Natty): | |
importance: | Undecided → High |
Changed in clamav (Ubuntu Oneiric): | |
importance: | Undecided → High |
Changed in clamav (Ubuntu Precise): | |
importance: | Undecided → High |
Changed in clamav (Ubuntu Natty): | |
milestone: | none → natty-updates |
Changed in clamav (Ubuntu Oneiric): | |
milestone: | none → oneiric-updates |
Changed in clamav (Ubuntu Precise): | |
milestone: | none → precise-updates |
description: | updated |
tags: | added: regression-release regression-update |
tags: | removed: regression-update |
Changed in clamav: | |
importance: | Unknown → Medium |
status: | Unknown → In Progress |
Changed in clamav (Debian): | |
status: | Unknown → Fix Released |
Changed in clamav: | |
status: | In Progress → Fix Released |
Users have reported that scanning MS compressed files are returning "CL_EFORMAT: Bad format or broken data ERROR". The patch for bug #4626 introduced this behavior. We are currently investigating the correct solution to these reports.