Protected-process code execution via unchecked DLL loading
Published May 20, 2022 · Updated Aug 3, 2024
DLL hijacking in Avast Premium Security before 21.11.2500 allows local users to execute code or interrupt the antivirus service. The instup.exe and wsc_proxy.exe processes seek nonexistent DLLs during REPAIR APP and load planted files without the expected security check. Administrative privileges and REPAIR APP invocation are required; exploitation runs code inside protected Avast processes or terminates antivirus.
Summary
What happened
DLL hijacking in Avast Premium Security before 21.11.2500 allows local users to execute code or interrupt the antivirus service. The instup.exe and wsc_proxy.exe processes seek nonexistent DLLs during REPAIR APP and load planted files without the expected security check. Administrative privileges and REPAIR APP invocation are required; exploitation runs code inside protected Avast processes or terminates antivirus.
The record
- CVE
- CVE-2022-28965
- Published
- May 20, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-427, T1562.001, T1574.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 20, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
No public exploit references are available in this record.
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