dbcve.org
Control For Beaglebone SlApplication · Codesys

CVE-2019-9010

CRITICAL · 9.8 CVSS v3.1 Published 2019-08-15
Fix available
A fix is available. Upgrade to 3.5.14.20 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An issue was discovered in 3S-Smart CODESYS V3 products. The CODESYS Gateway does not correctly verify the ownership of a communication channel. All variants of the following CODESYS V3 products in all versions prior to v3.5.14.20 that contain the CmpGateway component are affected, regardless of the CPU type or operating system: CODESYS Control for BeagleBone, CODESYS Control for emPC-A/iMX6, CODESYS Control for IOT2000, CODESYS Control for Linux, CODESYS Control for PFC100, CODESYS Control for PFC200, CODESYS Control for Raspberry Pi, CODESYS Control V3 Runtime System Toolkit, CODESYS Gateway V3, CODESYS V3 Development System.

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

The CODESYS Gateway V3 component fails to properly verify the ownership of communication channels, allowing an attacker to potentially hijack or impersonate legitimate communication sessions. This authentication/authorization bypass in the gateway affects all affected CODESYS V3 products regardless of CPU or OS platform.

MitigationUpgrade all affected CODESYS V3 products (runtime systems and gateway) to version v3.5.14.20 or later to obtain the patched CmpGateway component.

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
Control For Beaglebone SlApplication
Affected:>= 3.0, < 3.5.14.20
Control For Empc A\/imx6 SlApplication
Affected:>= 3.0, < 3.5.14.20
Control For Iot2000 SlApplication
Affected:>= 3.0, < 3.5.14.20
Control For Linux SlApplication
Affected:>= 3.0, < 3.5.14.20
Control For Pfc100 SlApplication
Affected:>= 3.0, < 3.5.14.20
Control For Pfc200 SlApplication
Affected:>= 3.0, < 3.5.14.20
Control For Raspberry Pi SlApplication
Affected:>= 3.0, < 3.5.14.20
Control Runtime ToolkitApplication
Affected:>= 3.0, < 3.5.14.20

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/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 checks

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

  1. Identify installed CODESYS products
    Locate CODESYS installation directories or check system for CODESYS Control runtime packages. Common locations include /opt/codesys, /etc/codesys, or C:\Program Files\CODESYS on Windows. Look for executables named CmpGateway, CODESYSControl, or gateway-related components.
    Affected if CODESYS Gateway V3 or any listed CODESYS Control runtime (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, Raspberry Pi) is present on the system
  2. Determine CODESYS Gateway version
    Query the installed CmpGateway component version. This may be available via: 1) gateway configuration file or log, 2) the CODESYS Development System under 'Gateway' properties, 3) running gateway status command if available, or 4) checking version metadata of the gateway executable or DLL.
    Affected if The retrieved Gateway version falls within range >= 3.0 and < 3.5.14.20
  3. Determine CODESYS Control runtime version
    For runtime systems, check the version of the CODESYS Control component. This may appear in system information, runtime logs, or can be queried through the CODESYS gateway when connected to the target device. Compare against the installed package version if visible in the system package manager.
    Affected if The runtime version is >= 3.0 and < 3.5.14.20 for any of the affected product lines (Beaglebone SL, Empc A/imx6 SL, IoT2000 SL, Linux SL, PFC100 SL, PFC200 SL, Raspberry Pi SL, or Runtime Toolkit)
  4. Verify gateway service status and configuration
    Check if the CODESYS Gateway service is running and listening on configured ports (typically TCP ports 1217, 1743, or 1740). Examine gateway configuration files for authentication and channel ownership settings. The vulnerability requires the gateway to be active and accessible.
    Affected if The gateway service is active and accessible, making the authentication bypass exploitable in practice

A system is affected if it runs any CODESYS V3 product with Gateway or Control Runtime version 3.0 or higher but below 3.5.14.20, with the gateway service enabled and reachable on the network.

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.

dbcve · scoped
Upgrade available Upgrade to 3.5.14.20 or later
Fixed in 3.5.14.20
Interim mitigation

Upgrade all affected CODESYS V3 products (runtime systems and gateway) to version v3.5.14.20 or later to obtain the patched CmpGateway component.

Recommended fix High confidence

CODESYS V3 version 3.5.14.20

  1. Identify the specific CODESYS V3 product(s) in your environment from the affected list (CODESYS Control for BeagleBone, emPC-A/iMX6, IOT2000, Linux, PFC100, PFC200, Raspberry Pi, or Control Runtime Toolkit)
  2. Determine the currently installed version of the affected CODESYS product(s)
  3. If the installed version is >= 3.0 and < 3.5.14.20, the system is vulnerable
  4. Obtain the fixed version 3.5.14.20 from the official CODESYS download source (customers.codesys.com)
  5. Review the release notes for version 3.5.14.20 to check for any compatibility considerations or migration requirements
  6. Plan an upgrade window and backup the current configuration
  7. Upgrade the CODESYS product(s) to version 3.5.14.20 or later
  8. Verify the upgrade was successful and the version is correctly reported
Caveat Review release notes before upgrading; minor version upgrades typically maintain backward compatibility but verify your specific use case

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Control For Beaglebone Sl Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-9010 — 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-2019-9010 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