319bfb51a5
290424 Missing break in switch - In hash_match: Missing break statement between cases in switch statement 290414 Resource leak - In cli_scanishield_msi: Leak of memory or pointers to system resources. Memory leak in a fail case 288197 Resource leak - In decrypt_any: Leak of memory or pointers to system resources. Memory leak in a fail case 290426 Resource leak - In cli_magic_scan: Leak of memory or pointers to system resources. Leaked a file prefix when running with --save-temps 192923 Resource leak - In cli_scanrar: Leak of memory or pointers to system resources. Leaked a file descriptor if a virus was found in a RAR file comment 225146 Resource leak - In cli_scanegg: Leak of memory or pointers to system resources. Leaked a file descriptor if unable to write a comment file to disk 290425 Resource leak - In scan_common: Leak of memory or pointers to system resources. Memory leaks in various fail cases. Also changes cli_scanrar to write out the file comment only if --leave-temps is specified and scan the buffer (like what is done in cli_scanegg) instead of writing the file out, scanning that, and then deleting the file if --leave-temps is not specified. The unit tests stopped working when correcting an issue with a switch statement that determined what type of signature had matched on a Google SafeBrowsing GDB rule. Looking into the unit tests, it looks like the code had always assumed that the test cases would be detected by a malware test rule in unit_tests/input/daily.gdb, but now some of the tests get matched on the phishing test rule. I updated the test logic to be more clear, and added tests for both cases now. Fix some memory leaks in libclamav/scanners.c |
||
|---|---|---|
| clamav-milter | ||
| clambc | ||
| clamconf | ||
| clamd | ||
| clamdscan | ||
| clamdtop | ||
| clamonacc | ||
| clamscan | ||
| clamsubmit | ||
| config | ||
| database | ||
| docs | ||
| etc | ||
| examples | ||
| freshclam | ||
| fuzz | ||
| libclamav | ||
| libclammspack | ||
| libclamunrar | ||
| libclamunrar_iface | ||
| libfreshclam | ||
| libltdl | ||
| llvm/lib/Target | ||
| m4 | ||
| shared | ||
| sigtool | ||
| test | ||
| unit_tests | ||
| win32 | ||
| .clang-format | ||
| .gitattributes | ||
| .gitignore | ||
| aclocal.m4 | ||
| ChangeLog.md | ||
| clam-format | ||
| clamav-config.h.in | ||
| clamav-config.in | ||
| clamav-types.h.in | ||
| clamav-version.h.in | ||
| configure | ||
| configure.ac | ||
| COPYING | ||
| COPYING.bzip2 | ||
| COPYING.curl | ||
| COPYING.file | ||
| COPYING.getopt | ||
| COPYING.LGPL | ||
| COPYING.llvm | ||
| COPYING.lzma | ||
| COPYING.pcre | ||
| COPYING.regex | ||
| COPYING.unrar | ||
| COPYING.YARA | ||
| COPYING.zlib | ||
| INSTALL.md | ||
| Jenkinsfile | ||
| libclamav.pc.in | ||
| Makefile.am | ||
| Makefile.in | ||
| NEWS.md | ||
| platform.h.in | ||
| README.md | ||
ClamAV
ClamAV® is an open source antivirus engine for detecting trojans, viruses, malware & other malicious threats.
Documentation & FAQ
Official documentation can be found online at ClamAV.net. Our source code release tarballs also includes a copy of the documentation for offline reading.
ClamAV Signatures
Anyone can learn to read and write ClamAV signatures. Take a look at the signature writing documentation and phishing signature writing documentation to get started!
Installation Instructions
UNIX
Build from Source on Linux/Unix/Mac
For basic compile and install instructions on Linux/Unix platforms, check out the install instructions.
For detailed instructions specific to building ClamAV please investigate our the Linux/Unix/Mac Install instructions in the User Manual.
Install from a binary package
For binary package distribution installation instructions, head over to our website.
Windows
Build from Source on Windows
The instructions for building ClamAV from source on Windows is located in the Win32 README.
Using an Install Package
We provide an installer to install ClamAV on Windows to "C:\Program Files". This install method will require you to have Adminstrator priveleges.
We also provide a "Portable Install Package" (i.e. a zip of the required files) for users that may wish to run ClamAV without installing it to a system-owned directory.
For details on how to use either option, head over to the Windows Install instructions in the User Manual.
Upgrading from a previous version
Some tips on how to upgrade from a previous version of ClamAV.
ClamAV News
For information about the features in this and prior releases, read the news.
Catch up on the latest about ClamAV by reading our blog and follow us on Twitter @clamav.
Join the ClamAV Community
The best way to get in touch with the ClamAV community is to join our our mailing lists, and tune to #clamav on IRC.
Want to make a contribution?
The ClamAV development team welcomes code contributions, improvements to our documentation, and also bug reports. Thanks for joining us!