Code execution via installer DLL search path
Published Oct 18, 2021 · Updated Aug 3, 2024
Code injection in GlassWire 2.1.167 allows attackers to execute arbitrary code via a crafted DLL loaded when its Windows installer first runs. The installer searches the user-controlled launch directory for DLL dependencies and loads a planted DLL instead of a trusted copy. Attackers must place the DLL in that directory and induce installer execution; the injected code then runs with the installer process privileges.
Summary
What happened
Code injection in GlassWire 2.1.167 allows attackers to execute arbitrary code via a crafted DLL loaded when its Windows installer first runs. The installer searches the user-controlled launch directory for DLL dependencies and loads a planted DLL instead of a trusted copy. Attackers must place the DLL in that directory and induce installer execution; the injected code then runs with the installer process privileges.
The record
- CVE
- CVE-2021-22961
- Published
- Oct 18, 2021
- Updated
- Aug 3, 2024
- Vendor
- SecureMix LLC
- Product
- GlassWire
- Classifications
- CWE-94, T1574.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 18, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed version 2.3.335
What conditions does exploitation require?
What is affected?
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