CVE-2018-14812
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 · uneditedAn uncontrolled search path element (DLL Hijacking) vulnerability has been identified in Fuji Electric Energy Savings Estimator versions V.1.0.2.0 and prior. Exploitation of this vulnerability could give an attacker access to the system with the same level of privilege as the application that utilizes the malicious DLL.
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 · high confidenceA DLL hijacking vulnerability exists in Fuji Electric Energy Savings Estimator versions 1.0.2.0 and prior, where the application loads Dynamic Link Libraries from an uncontrolled search path. An attacker can place a malicious DLL in a location where the application searches for DLLs, achieving code execution with the same privilege level as the application.
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 data= 1.0.2.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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.
-
Check if Fuji Electric Energy Savings Estimator is installedLook for the application in the program files directory or check the Windows uninstall registry for an entry named 'Fuji Electric Energy Savings Estimator'Affected if The application is not found on the system, then this CVE does not apply
-
Determine the installed versionRight-click the application executable, select Properties, and check the File Version field in the Details tab. Alternatively, check the version in Add or Remove ProgramsAffected if The version is 1.0.2.0 or any version prior to 1.0.2.0, indicating the installed version falls within the affected range
-
Verify the application uses vulnerable DLL loadingRun the application while monitoring DLL loading with tools such as Process Monitor, observing which DLLs the application attempts to load and from which pathsAffected if The application loads DLLs from directories in the search path that are user-writable or uncontrolled, indicating the DLL hijacking vulnerability is present
-
Confirm DLL search path configurationExamine the application's configuration or manifest files for any explicit DLL search path settingsAffected if No absolute paths are specified for DLL dependencies and no manifest-based side-by-side assemblies are configured, meaning the application relies on the default unsafe DLL search order
A system is affected by this CVE if Fuji Electric Energy Savings Estimator version 1.0.2.0 or prior is installed and the application loads DLLs from uncontrolled search paths, allowing potential DLL hijacking.
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 dataImplement secure DLL loading by specifying absolute paths for all DLL dependencies, using manifest-based side-by-side assemblies, or removing unsafe DLL search paths from the application's search order.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14812 — 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-2018-14812 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