CVE-2018-14790
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. A buffer over-read vulnerability may allow remote code execution on the device.
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 buffer over-read vulnerability exists in Fuji Electric FRENIC LOADER v3.3 v7.3.4.1a affecting multiple FRENIC inverter product lines. The vulnerability may allow remote code execution due to the memory access error, presenting a critical security risk in industrial control environments.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Identify if Fuji Electric FRENIC LOADER is installedCheck system inventory or installed programs for FRENIC LOADER software. Look for Fujielectric or FRENIC branding in installed applications or control system software lists.Affected if FRENIC LOADER version 7.3.4.1a is present on the system
-
Verify the installed version numberLocate the software version information through the application's About dialog, installation directory readme files, or Windows Add/Remove Programs details. Compare the exact version string to 7.3.4.1a.Affected if The installed version is exactly 7.3.4.1a (version equality, not a range)
-
Confirm the firmware version on connected invertersConnect to FRENIC inverter devices via FRENIC LOADER and query the firmware version. Check the inverter nameplate data or system configuration for firmware version 7.3.4.1a.Affected if Connected inverter firmware matches the affected loader version 7.3.4.1a
-
Determine if external/network communication is enabledInspect FRENIC LOADER connection settings and inverter network configuration. Check if external communication modules (Modbus, Ethernet, or fieldbus interfaces) are configured and active.Affected if The loader is configured to communicate with inverters over network interfaces, enabling the attack surface for remote exploitation
A system is affected if Fuji Electric FRENIC LOADER version 7.3.4.1a is installed and configured to communicate with inverter devices.
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 dataUpdate to vendor-provided patched versions of FRENIC LOADER; if patching is not immediately feasible, isolate affected systems from untrusted networks and monitor for exploitation attempts given the critical CVSS score.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14790 — 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-14790 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