Code execution via unqualified DLL loading
Published Apr 17, 2025 · Updated Apr 17, 2025
Uncontrolled DLL loading in OpenText Secure Content Manager 23.4 allows local users to execute code through its Windows thick client. The thick client requests DLLs without fully qualified paths, allowing Windows search order to load an attacker-controlled library from an unintended location. Exploitation requires write access arising from weak search-path folder permissions or another arbitrary file-write primitive, and the code runs in the client's trusted context.
Summary
What happened
Uncontrolled DLL loading in OpenText Secure Content Manager 23.4 allows local users to execute code through its Windows thick client. The thick client requests DLLs without fully qualified paths, allowing Windows search order to load an attacker-controlled library from an unintended location. Exploitation requires write access arising from weak search-path folder permissions or another arbitrary file-write primitive, and the code runs in the client's trusted context.
The record
- CVE
- CVE-2024-12530
- Published
- Apr 17, 2025
- Updated
- Apr 17, 2025
- Vendor
- OpenText
- Product
- Content Manager
- Classifications
- CWE-427, T1574.002
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 17, 2025CVE publishedPublication date reported by the CVE source.
- Apr 17, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=23.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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