CVE-2025-0664
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA locally authenticated, privileged user can craft a malicious OpenSSL configuration file, potentially leading the agent to load an arbitrary local library. This may impair endpoint defenses and allow the attacker to achieve code execution with SYSTEM-level privileges.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA locally authenticated, privileged user can craft a malicious OpenSSL configuration file that causes the agent to load an arbitrary local library, potentially impairing endpoint defenses and allowing code execution with SYSTEM-level privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- High
- Authentication
- Y
- User interaction
- None
- Scope
- N
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:Y/R:U/V:D/RE:L/U:Green
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenSSL installation and versionRun 'openssl version' and 'where openssl' (Windows) or 'which openssl' (Linux) to locate the OpenSSL binary and versionAffected if The installed OpenSSL version matches any affected range (compare to vendor advisories)
-
Locate OpenSSL configuration filesCheck common config locations: Windows: 'openssl.cnf' in OpenSSL install dir, %USERPROFILE%, or system32; Linux: /usr/ssl/openssl.cnf, /etc/ssl/openssl.cnf, or $OPENSSL_CONF environment variableAffected if OpenSSL config files exist and are accessible to privileged local users
-
Verify OpenSSL config file permissionsCheck file permissions using 'icacls' (Windows) or 'ls -la' (Linux) on the config file(s) found in previous stepAffected if Any non-admin or untrusted user has write access to OpenSSL config files
-
Inspect OpenSSL config for unsafe library pathsOpen the config file and search for directives: 'openssl_conf', 'ENGINEDIR', 'dynamic_path', or 'NULL' in config sections that may load external librariesAffected if Config contains directives allowing arbitrary library loading (e.g., dynamic_path pointing to user-writable locations)
-
Monitor for library injection indicatorsReview system for unexpected .dll/.so files in OpenSSL paths, check running processes for unsigned libraries loaded by OpenSSL-related services, review PowerShell 'Get-Process | Select-Object -ExpandProperty Modules' outputAffected if Unexpected or unsigned libraries are loaded in OpenSSL-related processes
A privileged local user can modify an OpenSSL configuration file to load arbitrary libraries, leading to SYSTEM-level code execution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict local administrative privileges, implement file integrity monitoring on OpenSSL configuration files, and validate OpenSSL config loading paths to prevent arbitrary library injection.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0664 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data