CVE-2019-18251
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 · uneditedIn Omron CX-Supervisor, Versions 3.5 (12) and prior, Omron CX-Supervisor ships with Teamviewer Version 5.0.8703 QS. This version of Teamviewer is vulnerable to an obsolete function vulnerability requiring user interaction to exploit.
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.5(12) and prior ship with an obsolete version of TeamViewer (5.0.8703 QS) that contains a known vulnerability in an obsolete function. The bundled TeamViewer component can be exploited through user interaction, allowing potential remote code execution or unauthorized access.
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.5\(12\)= 5.0.8703_qsCVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify CX-Supervisor installation and versionOpen Windows Control Panel, go to Programs and Features, locate 'Omron CX-Supervisor' in the installed programs list and note the version number displayed. Alternatively, check the installation directory for version information in the program files.Affected if The installed version is 3.5(12) or any version number lower than 3.5(12)
-
Locate bundled TeamViewer componentSearch for TeamViewer executable files within the CX-Supervisor installation directory. Common paths may include the main program folder or a subfolder named 'TeamViewer', 'SupportTools', or similar. Also check common TeamViewer installation paths on the system.Affected if TeamViewer executables (TeamViewer.exe, TeamViewer_Service.exe, or similar) are found in or alongside the CX-Supervisor installation
-
Determine TeamViewer versionRight-click the TeamViewer executable file, select Properties, and view the Details tab to read the Product Version. Alternatively, run 'TeamViewer.exe --version' from command prompt if supported, or view version info in Add/Remove Programs if TeamViewer appears as a separate installed program.Affected if The TeamViewer version is exactly 5.0.8703_qs or falls within the obsolete 5.0.x range
-
Verify TeamViewer service or process statusOpen Windows Task Manager or Services console and check if TeamViewer service is running, or if TeamViewer processes are active. Also check for scheduled tasks related to TeamViewer auto-start.Affected if The TeamViewer service is installed and set to run, or TeamViewer processes are currently active on the system
-
Check TeamViewer remote access configurationOpen TeamViewer if present, navigate to Extras > Options > Advanced, and review the incoming connection settings and security configurations. Check if unattended access or automatic acceptance of connections is enabled.Affected if TeamViewer is configured to accept incoming connections without manual confirmation, or unattended access is enabled
Your environment is affected if CX-Supervisor version 3.5(12) or prior is installed AND the bundled TeamViewer version 5.0.8703_qs is present, particularly if the TeamViewer service or remote access features are active.
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 the bundled TeamViewer component to a patched version, or upgrade to a newer CX-Supervisor release that ships with a secure TeamViewer version. If an official update is unavailable, consider removing or disabling the bundled TeamViewer if not required for operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18251 — 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-2019-18251 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