CVE-2017-20201: CCleaner v5.33.6162 & CCleaner Cloud v1.07.3191 Malicious Backdoor Supply Chain Compromise
CCleaner v5.33.6162 and CCleaner Cloud v1.07.3191 (32-bit builds) contained a malicious pre-entry-point loader that diverts execution from scrtcommonmainseh 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-20201?
CVE-2017-20201 has a high severity rating due to its potential for remote code execution.
How do I fix CVE-2017-20201?
To mitigate CVE-2017-20201, users should update CCleaner to version 5.34 or later.
Which software is affected by CVE-2017-20201?
CVE-2017-20201 affects CCleaner v5.33.6162 and CCleaner Cloud v1.07.3191 in their 32-bit builds.
What type of vulnerability is CVE-2017-20201?
CVE-2017-20201 is classified as a remote code execution vulnerability.
What are the potential impacts of CVE-2017-20201?
The impacts of CVE-2017-20201 include unauthorized access and execution of arbitrary code on affected systems.