clamav-base: ClamAV versions prior to 0.101.2 are susceptible to a denial of service (DoS) vulnerability
CVE-2019-1789 is fixed in 9 products on 1 platform, first by clamav 0.100.3+dfsg-0ubuntu0.18.04.1, released April 2, 2019. It is not reported as exploited. Patch Radar priority: Routine.
ClamAV versions prior to 0.101.2 are susceptible to a denial of service (DoS) vulnerability. An out-of-bounds heap read condition may occur when scanning PE files. An example is Windows EXE and DLL files that have been packed using Aspack as a result of inadequate bound-checking.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| clamav · Ubuntu 18.04.6 LTS (bionic) | 0.100.3+dfsg-0ubuntu0.18.04.1 | clamav 0.100.3+dfsg-0ubuntu0.18.04.1 | Apr 2, 2019 |
| clamav-base · Ubuntu 18.04.6 LTS (bionic) | 0.100.3+dfsg-0ubuntu0.18.04.1 | clamav-base 0.100.3+dfsg-0ubuntu0.18.04.1 | Apr 2, 2019 |
| clamav-daemon · Ubuntu 18.04.6 LTS (bionic) | 0.100.3+dfsg-0ubuntu0.18.04.1 | clamav-daemon 0.100.3+dfsg-0ubuntu0.18.04.1 | Apr 2, 2019 |
| clamav-docs · Ubuntu 18.04.6 LTS (bionic) | 0.100.3+dfsg-0ubuntu0.18.04.1 | clamav-docs 0.100.3+dfsg-0ubuntu0.18.04.1 | Apr 2, 2019 |
| clamav-freshclam · Ubuntu 18.04.6 LTS (bionic) | 0.100.3+dfsg-0ubuntu0.18.04.1 | clamav-freshclam 0.100.3+dfsg-0ubuntu0.18.04.1 | Apr 2, 2019 |
| clamav-milter · Ubuntu 18.04.6 LTS (bionic) | 0.100.3+dfsg-0ubuntu0.18.04.1 | clamav-milter 0.100.3+dfsg-0ubuntu0.18.04.1 | Apr 2, 2019 |
| clamav-testfiles · Ubuntu 18.04.6 LTS (bionic) | 0.100.3+dfsg-0ubuntu0.18.04.1 | clamav-testfiles 0.100.3+dfsg-0ubuntu0.18.04.1 | Apr 2, 2019 |
| clamdscan · Ubuntu 18.04.6 LTS (bionic) | 0.100.3+dfsg-0ubuntu0.18.04.1 | clamdscan 0.100.3+dfsg-0ubuntu0.18.04.1 | Apr 2, 2019 |
| libclamav7 · Ubuntu 18.04.6 LTS (bionic) | 0.100.3+dfsg-0ubuntu0.18.04.1 | libclamav7 0.100.3+dfsg-0ubuntu0.18.04.1 | Apr 2, 2019 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.