EUVD-2025-17356Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
3DescriptionCVE.org
Action1 Uncontrolled Search Path Element Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Action1. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.
The specific flaw exists within the configuration of OpenSSL. The product loads an OpenSSL configuration file from an unsecured location. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-26767.
AnalysisAI
Local privilege escalation vulnerability in Action1 where an attacker with low-privileged code execution can exploit an insecure OpenSSL configuration file loading mechanism to achieve SYSTEM-level code execution. The vulnerability requires prior code execution capability on the target system but presents a direct path to full system compromise once initial access is obtained. No active exploitation or public POC has been confirmed at this time, but the moderate CVSS score of 7.8 and CWE-427 classification indicate a meaningful risk to Action1 users.
Technical ContextAI
This vulnerability stems from CWE-427 (Uncontrolled Search Path Element), a path traversal weakness where Action1 loads OpenSSL configuration files from an unsecured or predictable location without proper validation. OpenSSL configuration files can contain directives that influence cryptographic operations, engine loading, and library paths. By placing a malicious openssl.cnf or related configuration file in a location that Action1's process will search before the legitimate system configuration, an attacker can inject arbitrary commands or load malicious libraries. The vulnerability likely affects Action1 versions that bundle or depend on OpenSSL without implementing proper search path restrictions. The specific CPE for Action1 would be 'cpe:2.3:a:action1:action1:*:*:*:*:*:*:*:*' with affected versions requiring vendor clarification.
RemediationAI
- Apply the latest Action1 security patch when released by the vendor (reference ZDI-CAN-26767 for tracking). 2. Implement principle of least privilege: run Action1 with minimum necessary privileges, avoiding SYSTEM or Administrator context where possible. 3. Restrict write permissions to directories where Action1 loads OpenSSL configuration files (typically Windows system paths like %WINDIR%\System32 and application installation directories). 4. Use file integrity monitoring (FIM) on OpenSSL configuration files and search paths to detect unauthorized modifications. 5. Isolate Action1 processes in AppContainers or similar sandboxes if Windows version supports it. 6. Monitor process creation and library loading from Action1 for anomalies.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to se
The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k
The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which mak
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
The X509_verify_cert function in crypto/x509/x509_vfy.c in OpenSSL 1.0.1n, 1.0.1o, 1.0.2b, and 1.0.2c does not properly
A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Rated hig
The ssl3_send_client_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before
In OpenSSL 1.1.0 before 1.1.0d, if a malicious server supplies bad parameters for a DHE or ECDHE key exchange then this
A denial of service flaw was found in OpenSSL 0.9.8, 1.0.1, 1.0.2 through 1.0.2h, and 1.1.0 in the way the TLS/SSL proto
Same weakness CWE-427 – Uncontrolled Search Path Element
View allShare
External POC / Exploit Code
Leaving vuln.today