ClamAV vulnerabilities

ClamAV before 0.98.6 allows remote attackers to have unspecified impact via a crafted upx packer file, related to a 'heap out of bounds condition.'

ClamAV before 0.98.6 allows remote attackers to have unspecified impact via a crafted Yoda's crypter or mew packer file, related to a 'heap out of bounds condition.'

ClamAV before 0.98.6 allows remote attackers to have unspecified impact via a crafted upack packer file, related to a 'heap out of bounds condition.'

A vulnerability in the XAR file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition or possibly other expanded impacts as a result of memory corruption. This is due to improper boundary checks for content in XAR files during scanning.

A vulnerability in the Mach-O file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition or possibly other expanded impacts as a result of memory corruption. This is due to improper boundary checks, which may result in an out-of-bounds buffer read.

A vulnerability in the PDF file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition or possibly other expanded impacts as a result of memory corruption. This is due to improper boundary checks, which may result in an out-of-bounds buffer read.

A vulnerability in the GPT file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition or possibly other expanded impacts as a result of memory corruption. This is due to improper handling of an endian conversion operation, which may result in an out-of-bounds buffer write.

A vulnerability in the PESpin file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition or possibly other impacts due to memory corruption. The issue is caused by improper boundary checks in PESpin files during scanning, which may result in an integer overflow. An attacker could exploit this by submitting a crafted file with PESpin content to be scanned by ClamAV.

A vulnerability in the zip archive parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition. The issue is due to improper memory handling when processing zip files during scanning. An attacker could exploit this by submitting a crafted zip file for scanning.

A vulnerability in the zip archive parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition. The issue is due to improper boundary checks for zip file content during scanning, which may result in an out-of-bounds write. An attacker could exploit this by submitting a crafted zip file for scanning.

A vulnerability in the DMG file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition or other impacts from memory corruption. The issue is due to improper boundary checks in DMG scanning, leading to integer overflow on 32-bit platforms only.

A vulnerability in the ALZ file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition or other impacts due to memory corruption. The issue stems from improper boundary checks in ALZ content, leading to an out-of-bounds buffer write.

A vulnerability in the PESpin file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition or other impacts due to memory corruption. The issue stems from improper boundary checks in PESpin files during scanning, potentially leading to an out-of-bounds buffer write.

A vulnerability in the InstallShield file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This is due to improper handling of temporary resources during file scanning.

A vulnerability in the 7z file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition or other impacts due to memory corruption. It is caused by improper boundary checks in 7z files during scanning, leading to an out-of-bounds buffer write.

A vulnerability in the FSG file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition, or possibly other impacts from memory corruption, on an affected device. It is due to improper boundary checks for content in FSG files during scanning, which may result in an out-of-bounds buffer write.

A vulnerability in the PE file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition due to memory corruption. The issue stems from improper boundary checks in PE files, leading to an out-of-bounds buffer write.