Arbitrary code execution via writable OPENSSLDIR
Published May 13, 2025 · Updated May 22, 2025
Local code execution in openssl-feedstock before 066e83c and Miniforge before 24.5.0 allows local users to run arbitrary code. The Windows build recipe compiles a writable build-time path into OPENSSLDIR, causing OpenSSL to read an attacker-controlled openssl.cnf and load its configured engine. A nonprivileged user must create that file and induce a process to load an affected DLL; execution inherits that process's privileges.
Summary
What happened
Local code execution in openssl-feedstock before 066e83c and Miniforge before 24.5.0 allows local users to run arbitrary code. The Windows build recipe compiles a writable build-time path into OPENSSLDIR, causing OpenSSL to read an attacker-controlled openssl.cnf and load its configured engine. A nonprivileged user must create that file and induce a process to load an affected DLL; execution inherits that process's privileges.
The record
- CVE
- CVE-2025-35471
- Published
- May 13, 2025
- Updated
- May 22, 2025
- Vendor
- conda-forge
- Product
- openssl-feedstock
- Classifications
- CWE-427, T1574
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2025CVE publishedPublication date reported by the CVE source.
- May 22, 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=0 <066e83c
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- OPENSSLDIR change in libcrypto-3-x64.dll between 24.3.0 and 24.5.0proof of concept · demonstrated
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