Vulnerabilities > Avast > Antivirus > 8.0.1504
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2020-04-01 | CVE-2020-10866 | Inadequate Encryption Strength vulnerability in Avast Antivirus An issue was discovered in Avast Antivirus before 20. | 7.5 |
| 2020-04-01 | CVE-2020-10865 | Inclusion of Functionality from Untrusted Control Sphere vulnerability in Avast Antivirus An issue was discovered in Avast Antivirus before 20. | 7.5 |
| 2020-04-01 | CVE-2020-10864 | Unspecified vulnerability in Avast Antivirus An issue was discovered in Avast Antivirus before 20. | 6.5 |
| 2020-04-01 | CVE-2020-10863 | Unspecified vulnerability in Avast Antivirus An issue was discovered in Avast Antivirus before 20. | 7.5 |
| 2020-04-01 | CVE-2020-10862 | Unspecified vulnerability in Avast Antivirus An issue was discovered in Avast Antivirus before 20. | 7.8 |
| 2020-04-01 | CVE-2020-10861 | Unspecified vulnerability in Avast Antivirus An issue was discovered in Avast Antivirus before 20. | 7.5 |
| 2020-04-01 | CVE-2020-10860 | Out-of-bounds Write vulnerability in Avast Antivirus An issue was discovered in Avast Antivirus before 20. | 7.5 |
| 2019-10-23 | CVE-2019-17093 | Uncontrolled Search Path Element vulnerability in multiple products An issue was discovered in Avast antivirus before 19.8 and AVG antivirus before 19.8. | 7.8 |
| 2019-07-18 | CVE-2019-11230 | Link Following vulnerability in Avast Antivirus In Avast Antivirus before 19.4, a local administrator can trick the product into renaming arbitrary files by replacing the Logs\Update.log file with a symlink. | 4.4 |
| 2017-04-27 | CVE-2017-8308 | Improper Privilege Management vulnerability in Avast Antivirus In Avast Antivirus before v17, an unprivileged user (and thus malware or a virus) can mark an arbitrary process as Trusted from the perspective of the Avast product. | 7.5 |