Vulnerability Description
Avast AntiTrack before 1.5.1.172 and AVG Antitrack before 2.0.0.178 proxies traffic to HTTPS sites but does not validate certificates, and thus a man-in-the-middle can host a malicious website using a self-signed certificate. No special action necessary by the victim using AntiTrack with "Allow filtering of HTTPS traffic for tracking detection" enabled. (This is the default configuration.)
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Avast | Antitrack | < 1.5.1.172 |
| Avast | Avg Antitrack | < 2.0.0.178 |
Related Weaknesses (CWE)
References
- https://www.avast.com/hacker-hall-of-fame/en/researcher-david-eade-reports-antitVendor Advisory
- https://www.davideade.com/2020/03/avast-antitrack.htmlThird Party Advisory
- https://www.avast.com/hacker-hall-of-fame/en/researcher-david-eade-reports-antitVendor Advisory
- https://www.davideade.com/2020/03/avast-antitrack.htmlThird Party Advisory
FAQ
What is CVE-2020-8987?
CVE-2020-8987 is a vulnerability with a CVSS score of 7.4 (HIGH). Avast AntiTrack before 1.5.1.172 and AVG Antitrack before 2.0.0.178 proxies traffic to HTTPS sites but does not validate certificates, and thus a man-in-the-middle can host a malicious website using a...
How severe is CVE-2020-8987?
CVE-2020-8987 has been rated HIGH with a CVSS base score of 7.4/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2020-8987?
Check the references section above for vendor advisories and patch information. Affected products include: Avast Antitrack, Avast Avg Antitrack.