CVE-2018-14798
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 · uneditedFuji Electric FRENIC LOADER v3.3 v7.3.4.1a of FRENIC-Mini (C1), FRENIC-Mini (C2), FRENIC-Eco, FRENIC-Multi, FRENIC-MEGA, FRENIC-Ace. The program does not properly parse FNC files that may allow for information disclosure.
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 confidenceFuji Electric FRENIC LOADER v3.3 v7.3.4.1a contains a vulnerability where the software does not properly parse FNC (configuration) files, potentially allowing an attacker to craft malicious FNC files that disclose sensitive information when opened by the software.
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= 7.3.4.1aCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Confirm FRENIC Loader installationLocate the Fuji Electric FRENIC Loader application on the system. Check the installed programs list, program files directory, or the software's About/Help section for product identification.Affected if The software Fuji Electric FRENIC Loader is present on the system.
-
Identify installed versionAccess the software's About dialog, Help menu, or check the version information in the program's properties (right-click executable → Properties → Details). Look for version string '7.3.4.1a'.Affected if The installed version is exactly 7.3.4.1a.
-
Verify FNC file handling capabilityCheck if FNC file type associations exist on the system. Look for .fnc file extension registration in Windows Registry under HKCR\.fnc or HKLM\Software\Classes\.fnc, or check if the software lists FNC as a supported file type.Affected if FNC file type is registered or the software explicitly supports opening FNC configuration files.
-
Review recent FNC file activityCheck the system for recently opened or modified FNC files. Search for .fnc files in user directories, recent documents, or the software's working folder.Affected if FNC files have been opened with FRENIC Loader, indicating the vulnerable parsing code path was executed.
A user is affected if Fuji Electric FRENIC Loader version 7.3.4.1a is installed AND the software is used to open or process FNC configuration files.
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 dataUsers should avoid opening untrusted FNC files from unknown or unverified sources. Apply vendor patches when available. Consider running the software in a restricted environment to limit exposure if the vulnerability is exploited.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14798 — 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-14798 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