dbcve.org
Cx FlnetApplication · Omron

CVE-2018-7514

HIGH · 7.8 CVSS v3.1 Published 2018-04-17
Fix available
A fix is available. Upgrade to after 9.65 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Parsing malformed project files in Omron CX-One versions 4.42 and prior, including the following applications: CX-FLnet versions 1.00 and prior, CX-Protocol versions 1.992 and prior, CX-Programmer versions 9.65 and prior, CX-Server versions 5.0.22 and prior, Network Configurator versions 3.63 and prior, and Switch Box Utility versions 1.68 and prior, may cause a stack-based buffer overflow.

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 confidence

A stack-based buffer overflow vulnerability in Omron CX-One suite (versions 4.42 and prior) allows remote code execution or denial of service when parsing malformed project files. The vulnerability affects multiple applications including CX-Programmer, CX-Protocol, CX-Server, Network Configurator, CX-FLnet, and Switch Box Utility.

MitigationUpdate all affected Omron CX-One applications to versions newer than those specified (post 4.42 for CX-One suite, and post-specific versions for each component). Until patched, avoid opening untrusted project files from unknown sources.

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
Cx FlnetApplication
Affected:<= 1.00
Cx OneApplication
Affected:<= 4.42
Cx ProgrammerApplication
Affected:<= 9.65
Cx ProtocolApplication
Affected:<= 1.992
Cx ServerApplication
Affected:<= 5.0.22
Network ConfiguratorApplication
Affected:<= 3.63
Switch Box UtilityApplication
Affected:<= 1.68

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Omron CX-One applications
    Open Windows Control Panel > Programs and Features, or use 'Get-ItemProperty' in PowerShell to list installed programs containing 'Omron', 'CX-One', 'CX-Programmer', 'CX-Protocol', 'CX-Server', 'Network Configurator', 'CX-FLnet', or 'Switch Box Utility'
    Affected if any of the listed Omron applications appear in the installed programs list
  2. Check CX-One suite version
    Look for CX-One version in the installed programs list, or check the version of cxoneinst.exe or related installer files if present, or open any CX-One application and go to Help > About
    Affected if version displayed is 4.42 or lower
  3. Check CX-Programmer version
    Open CX-Programmer, go to Help > About CX-Programmer, or check the executable properties of cxp.exe in the installation directory
    Affected if version shown is 9.65 or lower
  4. Check CX-Protocol version
    Open CX-Protocol and check Help > About, or examine the version property of the protocol.exe executable
    Affected if version shown is 1.992 or lower
  5. Check CX-Server version
    Check the version of CX-Server in Add/Remove Programs, or inspect the cxsrv.exe properties in the installation folder
    Affected if version shown is 5.0.22 or lower
  6. Check Network Configurator, CX-FLnet, and Switch Box Utility versions
    Check each application's Help > About dialog or examine the executable properties in their respective installation directories
    Affected if Network Configurator is 3.63 or lower, CX-FLnet is 1.00 or lower, or Switch Box Utility is 1.68 or lower

You are affected if any of the six Omron CX-One components are installed at a version at or below the thresholds listed, and the system processes or opens project files from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 9.65
Interim mitigation

Update all affected Omron CX-One applications to versions newer than those specified (post 4.42 for CX-One suite, and post-specific versions for each component). Until patched, avoid opening untrusted project files from unknown sources.

Fix this in Cx Flnet Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7514 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-7514 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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