System reboot via low-integrity RPC request
Published Apr 1, 2020 · Updated Aug 4, 2024
Denial of service in Avast Antivirus before 20 allows local users to reboot Windows through the aswTask RPC endpoint. The TaskEx library in AvastSvc.exe accepts a reboot RPC request from a Low Integrity process without enforcing the intended trust boundary. Exploitation requires code running in a Low Integrity Windows process, and successful use forces a system reboot without reported data exposure or modification.
Summary
What happened
Denial of service in Avast Antivirus before 20 allows local users to reboot Windows through the aswTask RPC endpoint. The TaskEx library in AvastSvc.exe accepts a reboot RPC request from a Low Integrity process without enforcing the intended trust boundary. Exploitation requires code running in a Low Integrity Windows process, and successful use forces a system reboot without reported data exposure or modification.
The record
- CVE
- CVE-2020-10864
- Published
- Apr 1, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1529
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 1, 2020CVE 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 aswTask RPC reboot demonstrationproof of concept · 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