SYSTEM privilege escalation via Task Scheduler IPC
Published Dec 27, 2021 · Updated Aug 4, 2024
Privilege escalation in Avast Antivirus before 20.4 allows local users to escape the Sandbox component and execute code as SYSTEM. The sandboxed aswEngSrv.exe process retains a restricted SYSTEM token, and Task Scheduler checks only its SYSTEM owner when registering tasks. Code must already run inside the antivirus sandbox; registering a scheduled task then launches unrestricted attacker code as SYSTEM.
Summary
What happened
Privilege escalation in Avast Antivirus before 20.4 allows local users to escape the Sandbox component and execute code as SYSTEM. The sandboxed aswEngSrv.exe process retains a restricted SYSTEM token, and Task Scheduler checks only its SYSTEM owner when registering tasks. Code must already run inside the antivirus sandbox; registering a scheduled task then launches unrestricted attacker code as SYSTEM.
The record
- CVE
- CVE-2021-45336
- Published
- Dec 27, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-284, T1053.005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Avast Sandbox Task Scheduler escape proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo