p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in clamav · Seite 2

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für clamav: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 22

  1. CVE-2024-20328

    Mittel · CVSS 5.3EPSS 84,84%Korrektur verfügbar

    ClamAV VirusEvent File Processing Command Injection Vulnerability

    A vulnerability in the VirusEvent feature of ClamAV could allow a local attacker to inject arbitrary commands with the privileges of the application service account.The vulnerability is due to unsafe handling of file names. A local attacker could exploit this vulnerability by supplying a file name containing command-line sequences. When processed on a system using configuration options for the VirusEvent feature, the attacker could cause the application to execute arbitrary commands. ClamAV has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

    • Auf 1.0.5+dfsg-1ubuntu1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2024-20290

    Hoch · CVSS 7.5EPSS 33,32%Korrektur verfügbar

    CVE-2024-20290

    A vulnerability in the OLE2 file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to an incorrect check for end-of-string values during scanning, which may result in a heap buffer over-read. An attacker could exploit this vulnerability by submitting a crafted file containing OLE2 content to be scanned by ClamAV on an affected device. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software and consuming available system resources.

    • Auf 1.0.5+dfsg-1ubuntu1 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →