Code execution via PMHook.dll search-order hijacking
Published May 12, 2023 · Updated Jan 24, 2025
DLL hijacking in Soft-o Free Password Manager 1.1.20 allows local users to execute code through a malicious PMHook.dll file. The application loads PMHook.dll from a target system directory whose contents can be influenced, allowing a planted library to replace the expected module. The victim must start the application after the DLL is planted, and the payload executes with the victim's privileges.
Summary
What happened
DLL hijacking in Soft-o Free Password Manager 1.1.20 allows local users to execute code through a malicious PMHook.dll file. The application loads PMHook.dll from a target system directory whose contents can be influenced, allowing a planted library to replace the expected module. The victim must start the application after the DLL is planted, and the payload executes with the victim's privileges.
The record
- CVE
- CVE-2023-25428
- Published
- May 12, 2023
- Updated
- Jan 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-427, T1574.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2023CVE publishedPublication date reported by the CVE source.
- Jan 24, 2025Record 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
- Soft-o Free Password Manager 1.1.20 DLL Hijackingproof of concept · unverified
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