CVE-2022-25999
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 · uneditedUncontrolled search path element in the Intel(R) Enpirion(R) Digital Power Configurator GUI software, all versions may allow an authenticated user to potentially enable escalation of privilege via local access.
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 confidenceThis is an untrusted search path vulnerability (DLL hijacking) in Intel's Enpirion Digital Power Configurator GUI. The application loads libraries from insecure paths, allowing an authenticated local user to place malicious DLLs in directories the application searches, resulting in privilege escalation from their current user level to higher privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify if Intel Enpirion Digital Power Configurator GUI is installedLook for the application in the system installed programs list or search for the executable file on the systemAffected if The application is present on the system
-
Identify the application's search path for DLLsRun the application while monitoring DLL loading using Process Monitor or similar tooling to see which directories it queries for DLL filesAffected if The application loads DLLs from directories writable by lower-privileged users
-
Check write permissions on application directoryInspect file system permissions on the directory where the application is installed to determine which users can create or modify filesAffected if Non-admin users have write access to the application's installation directory
-
Review PATH environment variable for writable locationsCheck each directory listed in the system or user PATH environment variable for write access by untrusted usersAffected if Any PATH directory is writable by authenticated local users who are not administrators
-
Audit for unexpected DLLs in search pathsCompare DLL files in the application directory and PATH directories against known-good baselines or look for recently created suspicious DLLsAffected if Unexpected or newly placed DLL files exist in directories the application searches
If the Intel Enpirion Digital Power Configurator GUI is installed and any directory in its DLL search path is writable by an authenticated non-admin user, that user could potentially place a malicious DLL to achieve privilege escalation.
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 dataApply the vendor patch when available. In the interim, ensure only trusted users have write access to directories in the application's search path and remove any unnecessary directories from PATH.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25999 — 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-2022-25999 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