{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20202 exists.","fix":"No fix has been published for CVE-2017-20202 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-20202 is a critical vulnerability in Web Developer for Chrome, published on 8 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-20202 and fix it if it is affected.\n\nWhat it is: CVE-2017-20202 is a critical vulnerability in Web Developer for Chrome, published on 8 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20202 exists.\n\nAffected product: Web Developer for Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-20202/ (Markdown: https://insights.sbomify.com/CVE-2017-20202/index.md)","id":"CVE-2017-20202","markdown":"https://insights.sbomify.com/CVE-2017-20202/index.md","name":"CVE-2017-20202","record":{"aliases":["GHSA-vwvp-p3cc-rrj2"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Chrome extension","requires_auth":"none","summary":"A malicious backdoor in the Web Developer Chrome extension enabled code execution, credential theft, and ad fraud via a supply chain compromise.","user_interaction":"required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-506","name":"Embedded Malicious Code"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Web Developer for Chrome v0.4.9 Malicious Backdoor Supply Chain Compromise","id":"CVE-2017-20202","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2017"},"n_packages":0,"n_references":6,"next":{"headline":"NetSarang v5.0 Malicious Backdoor Supply Chain Compromise","id":"CVE-2017-20203"},"packages":[],"prev":{"headline":"CCleaner v5.33.6162 \u0026 CCleaner Cloud v1.07.3191 Malicious Backdoor Supply Chain Compromise","id":"CVE-2017-20201"},"products":["Web Developer for Chrome"],"published":"2025-10-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-14","vendors":["Web Developer for Chrome"]},"summary":"A malicious backdoor in the Web Developer Chrome extension enabled code execution, credential theft, and ad fraud via a supply chain compromise.","url":"https://insights.sbomify.com/CVE-2017-20202/"}