Arbitrary code execution via DLL search order
Published Jul 26, 2021 · Updated Aug 4, 2024
DLL hijacking in 1Password for Windows 7.3.712 allows local users to execute arbitrary code through a planted library. The 1password.dll module resolves five system DLL names from its application directory instead of restricting resolution to trusted system copies. Execution requires a crafted DLL in the searched directory and user interaction to start the affected process; the payload then runs inside 1Password.
Summary
What happened
DLL hijacking in 1Password for Windows 7.3.712 allows local users to execute arbitrary code through a planted library. The 1password.dll module resolves five system DLL names from its application directory instead of restricting resolution to trusted system copies. Execution requires a crafted DLL in the searched directory and user interaction to start the affected process; the payload then runs inside 1Password.
The record
- CVE
- CVE-2020-18173
- Published
- Jul 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-427, T1574.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 26, 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
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