CVE-2018-17905
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 · uneditedWhen processing project files in Omron CX-Supervisor Versions 3.4.1.0 and prior and tampering with a specific byte, memory corruption may occur within a specific object.
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 confidenceOmron CX-Supervisor versions 3.4.1.0 and prior contain a memory corruption vulnerability when processing project files. An attacker can trigger the vulnerability by tampering with a specific byte in a project file, causing memory corruption within a specific object, potentially leading to arbitrary code execution.
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<= 3.4.1.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.
-
Locate CX-Supervisor installation directoryCheck common installation paths such as C:\Program Files\Omron\CX-Supervisor or C:\Program Files (x86)\Omron\CX-Supervisor. Use file explorer or command: dir /s /b "C:\Program Files\Omron" 2>nul or dir /s /b "C:\Program Files (x86)\Omron" 2>nulAffected if The CX-Supervisor folder exists on the system
-
Identify installed CX-Supervisor versionLocate the executable file (typically Supervisor.exe or similar) in the installation folder. Right-click the executable, select Properties, and check the Version tab. Alternatively, run: powershell "Get-ItemProperty 'C:\Program Files\Omron\CX-Supervisor\*.exe' | Select-Object Name, VersionInfo"Affected if The version displayed is 3.4.1.0 or any version lower than 3.4.1.0
-
Check for presence of project filesSearch for .supervisor, .sup, or project file extensions associated with CX-Supervisor in the system. Use: powershell "Get-ChildItem -Path 'C:\' -Recurse -Include *.supervisor,*.sup -ErrorAction SilentlyContinue | Select-Object FullName" (this may take time; narrow search to known project directories)Affected if Project files exist and the CX-Supervisor version is 3.4.1.0 or lower
-
Verify the vulnerable component is presentConfirm the CX-Supervisor executable responsible for loading project files exists in the installation directory. Check for files related to project file parsing or runtime modulesAffected if The CX-Supervisor software is installed with project file handling capabilities and the version is 3.4.1.0 or lower
The environment is affected if Omron CX-Supervisor version 3.4.1.0 or earlier is installed and the software has access to project 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 dataUpgrade to a version newer than 3.4.1.0 when available from Omron. If no patch is available, implement compensating controls: restrict access to project files via file system permissions, enable file integrity monitoring, and apply network segmentation to limit exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17905 — 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-17905 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