CVE-2017-20202
CRITICALDescription
Web Developer for Chrome v0.4.9 contained malicious code that generated a domain via a DGA and fetched a remote script. The fetched script conditionally loaded follow-on modules that performed extensive ad substitution and malvertising, displayed fake “repair” alerts that redirected users to affiliate programs, and attempted to harvest credentials when users logged in. Injected components enumerate common banner sizes for substitution, replace third-party ad calls, and redirect victim traffic to affiliate landing pages. Potential impacts include user-level code execution in the browser context, large-scale ad fraud and traffic hijacking, credential theft, and exposure to additional payloads delivered by the actor. The compromise was reported on by the maintainer of Web Developer for Chrome on August 2, 2017 and remediated in v0.5.0.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Moderate risk: more likely to be exploited than 44% of all known CVEs.
References
Related Vulnerabilities
Other CWE-506 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-3094 | Critical | 10.0 | 86% | - | Fix |
| CVE-2025-30066 | High | 8.6 | 70% | KEV | - |
| CVE-2026-33634 | High | 8.8 | 59% | KEV | Fix |
| CVE-2024-4978 | High | 8.4 | 27% | KEV | - |
| CVE-2025-54313 | High | 7.5 | 4.3% | KEV | Fix |
| CVE-2025-30154 | High | 8.6 | 2.4% | KEV | Fix |
Common questions
How do I fix CVE-2017-20202?
No published fix for CVE-2017-20202 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2017-20202 being actively exploited?
Not that we know of. CVE-2017-20202 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.53% is the estimated probability that it will be exploited in the next 30 days. That is higher than 44% of all scored CVEs.
How severe is CVE-2017-20202?
CVE-2017-20202 has a CVSS v4 base score of 9.3, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2017-20202
Markdown
[](https://tridentstack.com/cve/CVE-2017-20202)HTML
<a href="https://tridentstack.com/cve/CVE-2017-20202"><img src="https://tridentstack.com/cve/badge/CVE-2017-20202.svg" alt="CVE-2017-20202"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-17.