CVE-2017-20201
Last modified
CVE-2017-20201 is a critical-severity vulnerability rated 9.3/10 on the CVSS scale. CCleaner v5.33.6162 and CCleaner Cloud v1.07.3191 (32-bit builds) contained a malicious pre-entry-point loader that diverts execution from __scrt_common_main_seh into a custom loader. That loader decodes an embedded blob into shellcode, allocates executable heap memory, resolves Windows API functions at runtime, and transfers execution to an in-memory payload. EPSS estimates a 0.48% chance of exploitation in the next 30 days.
Description
CCleaner v5.33.6162 and CCleaner Cloud v1.07.3191 (32-bit builds) contained a malicious pre-entry-point loader that diverts execution from __scrt_common_main_seh into a custom loader. That loader decodes an embedded blob into shellcode, allocates executable heap memory, resolves Windows API functions at runtime, and transfers execution to an in-memory payload. The payload performs anti-analysis checks, gathers host telemetry, encodes the data with a two-stage obfuscation, and attempts HTTPS exfiltration to hard-coded C2 servers or month-based DGA domains. Potential impacts include remote data collection and exfiltration, stealthy in-memory execution and persistence, and potential lateral movement. CCleaner was developed by Piriform, which was acquired by Avast in July 2017; Avast later merged with NortonLifeLock to form the parent company now known as Gen Digital. According to vendor advisories, the compromised CCleaner build was released on August 15, 2017 and remediated on September 12, 2017 with v5.34; the compromised CCleaner Cloud build was released on August 24, 2017 and remediated on September 15, 2017 with v1.07.3214.
Metrics
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
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2017-20201?
How severe is CVE-2017-20201?
How do I fix CVE-2017-20201?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-20196A vulnerability was found in Itechscripts School Management …6.3
- CVE-2017-20197A vulnerability was found in propanetank Roommate-Bill-Track…7.3
- CVE-2017-20198The Marathon UI in DC/OS < 1.9.0 allows unauthenticated user…9.3
- CVE-2017-20199A vulnerability was found in Buttercup buttercup-browser-ext…6.5
- CVE-2017-2020Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2017-20200A vulnerability has been found in Coinomi up to 1.7.6. This …3.7
- CVE-2017-20202Web Developer for Chrome v0.4.9 contained malicious code tha…9.3
- CVE-2017-20203NetSarang Xmanager Enterprise 5.0 Build 1232, Xmanager 5.0 B…9.3
- CVE-2017-20204DBLTek GoIP devices (models GoIP 1, 4, 8, 16, and 32) contai…9.3
- CVE-2017-20205Valve's Source SDK (source-sdk-2013)'s ragdoll model parsing…9.2
- CVE-2017-20206The Appointments plugin for WordPress is vulnerable to PHP O…9.8
- CVE-2017-20207The Flickr Gallery plugin for WordPress is vulnerable to PHP…9.8
Are you affected by CVE-2017-20201?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
