Local code execution via current-directory DLL loading
Published Apr 17, 2020 · Updated Aug 5, 2024
DLL hijacking in LG PC Suite 5.3.27 and earlier allows local users to execute arbitrary code through a Trojan horse DLL. The application searches the current working directory for a DLL and loads an attacker-controlled library without constraining the lookup to a trusted path. Exploitation requires user interaction and placement of the crafted DLL in that directory; the loaded code runs with the application's privileges.
Summary
What happened
DLL hijacking in LG PC Suite 5.3.27 and earlier allows local users to execute arbitrary code through a Trojan horse DLL. The application searches the current working directory for a DLL and loads an attacker-controlled library without constraining the lookup to a trusted path. Exploitation requires user interaction and placement of the crafted DLL in that directory; the loaded code runs with the application's privileges.
The record
- CVE
- CVE-2019-20769
- Published
- Apr 17, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-427, T1574.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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