Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-12530 Overview
CVE-2024-12530 is an Uncontrolled Search Path Element vulnerability [CWE-427] in OpenText Secure Content Manager on Windows. The flaw affects Secure Content Manager version 23.4 and enables DLL side-loading attacks against the thick-client application. An attacker who places a malicious Dynamic Link Library (DLL) in a location searched by the application can execute arbitrary code within the trusted process context. Exploitation requires local access and user interaction, limiting remote attack scenarios. The vulnerability allows end-users to run malicious code with the privileges and trust of the Secure Content Manager client.
Critical Impact
Successful exploitation grants arbitrary code execution in the trusted context of the OpenText Secure Content Manager thick-client, compromising confidentiality, integrity, and availability.
Affected Products
- OpenText Secure Content Manager 23.4
- Windows platform deployments of the thick-client application
- Environments that permit user-writable directories in the DLL search path
Discovery Timeline
- 2025-04-17 - CVE-2024-12530 published to the National Vulnerability Database (NVD)
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-12530
Vulnerability Analysis
The vulnerability stems from the application failing to specify fully qualified paths when loading DLLs at runtime. Windows resolves unqualified DLL names through a defined search order that includes the application directory, current working directory, and directories in the PATH environment variable. When any of these locations are writable by a lower-privileged user, an attacker can plant a malicious DLL that matches the name expected by Secure Content Manager. The loader then maps the attacker-controlled library into the trusted process. Code in the malicious DLL executes with the same privileges as the Secure Content Manager thick-client, bypassing application-level trust boundaries.
Root Cause
The root cause is Uncontrolled Search Path Element [CWE-427]. OpenText Secure Content Manager 23.4 resolves one or more dependent libraries using the default Windows DLL search order rather than loading libraries from a verified absolute path. The application also does not enforce signature validation on loaded modules, so any DLL with a matching filename is accepted.
Attack Vector
The attack vector is local and requires user interaction. An attacker needs the ability to write a DLL to a directory that falls within the application's search order, or must convince a user to open a Secure Content Manager document from a controlled working directory. When the user launches the application or triggers the vulnerable code path, Windows loads the malicious DLL. The payload then runs under the identity of the Secure Content Manager process. See the Micro Focus Knowledge Article for vendor technical details.
No verified exploit code is publicly available for this vulnerability. Technical implementation details are described in prose rather than reproduced here.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2024-12530
Indicators of Compromise
- Unsigned or unexpected DLL files present in the Secure Content Manager installation directory or adjacent user-writable paths
- DLL files with timestamps that do not match the official OpenText installer manifest
- Secure Content Manager processes loading modules from user profile directories, %TEMP%, or network shares
Detection Strategies
- Monitor image load events (Sysmon Event ID 7) for the Secure Content Manager executable and alert on loads from non-standard directories
- Baseline the expected DLL set shipped with Secure Content Manager 23.4 and flag deviations in file integrity monitoring
- Hunt for process creation chains where Secure Content Manager spawns unexpected child processes such as cmd.exe, powershell.exe, or rundll32.exe
Monitoring Recommendations
- Enable PowerShell script block and command-line logging to capture downstream payload execution
- Collect endpoint telemetry on file write operations targeting directories within the application search path
- Correlate authenticated user activity with DLL creation events to identify staging of malicious libraries
How to Mitigate CVE-2024-12530
Immediate Actions Required
- Inventory all Windows endpoints running OpenText Secure Content Manager 23.4 and prioritize them for remediation
- Restrict write permissions on the Secure Content Manager installation directory and any directories in the application's DLL search path
- Review the Micro Focus Knowledge Article KM000040073 for vendor-supplied remediation guidance
Patch Information
OpenText has published remediation guidance through the Micro Focus support portal. Administrators should consult the Micro Focus Knowledge Article for the fixed version and upgrade procedure applicable to Secure Content Manager 23.4 deployments. Apply the vendor-supplied update to all affected Windows clients.
Workarounds
- Remove the current working directory from the DLL search path by setting the SafeDllSearchMode and CWDIllegalInDllSearch registry values to safer defaults
- Apply AppLocker or Windows Defender Application Control (WDAC) policies that permit only signed DLLs to load within the Secure Content Manager process
- Launch Secure Content Manager only from protected directories where standard users lack write access
# Configuration example: enforce safe DLL search mode via registry
reg add "HKLM\System\CurrentControlSet\Control\Session Manager" /v SafeDllSearchMode /t REG_DWORD /d 1 /f
reg add "HKLM\System\CurrentControlSet\Control\Session Manager" /v CWDIllegalInDllSearch /t REG_DWORD /d 0xFFFFFFFF /f
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

