dbcve.org
Control For Beaglebone SlApplication · Codesys

CVE-2019-9012

HIGH · 7.5 CVSS v3.1 Published 2019-08-15
Fix available
A fix is available. Upgrade to 3.5.14.20 or later.
See remediation →
84/100
Remediation priority · High
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. A crafted communication request may cause uncontrolled memory allocations in the affected CODESYS products and may result in a denial-of-service condition. 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

A memory exhaustion vulnerability in the CmpGateway component of CODESYS V3 products allows remote attackers to cause uncontrolled memory allocations via crafted communication requests, leading to denial of service. The vulnerability affects multiple CODESYS Control runtime products and the Gateway V3 component running versions prior to v3.5.14.20.

MitigationUpdate all affected CODESYS V3 products to version v3.5.14.20 or later to patch the uncontrolled memory allocation vulnerability in the 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 product
    Locate the CODESYS Control runtime installed on the system. Common products include Codesys Control for Beaglebone, Raspberry Pi, Linux, Empc A/imx6, IoT2000, PFC100, PFC200, or the CODESYS Control Runtime Toolkit. Check the product name and installation directory.
    Affected if The installed product is any of the affected products listed in the CVE with version >= 3.0 and < 3.5.14.20
  2. Check CODESYS runtime version
    Use the product-specific method to query the installed CODESYS version. For runtime products, this is typically found in the product information, control runtime settings, or about dialog. Compare the version number against the affected range (>= 3.0, < 3.5.14.20).
    Affected if The installed version is 3.0 or higher but below 3.5.14.20
  3. Verify CmpGateway component is in use
    Check if the CmpGateway component is loaded or active in the CODESYS runtime. This component handles network communication between CODESYS devices. Look for gateway-related processes, services, or configurations in the CODESYS installation.
    Affected if The CmpGateway component is loaded, running, or exposed on the network
  4. Check Gateway V3 exposure
    Inspect the network configuration to determine if the CODESYS Gateway V3 service is listening on network ports (default port 1217). Verify if remote connections are accepted or if the gateway is accessible from other devices.
    Affected if Gateway V3 is running and accessible on the network, allowing remote communication requests

If the CODESYS product version is >= 3.0 and < 3.5.14.20 and the CmpGateway/Gateway V3 component is active, the environment is vulnerable to memory exhaustion attacks via crafted requests.

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 3.5.14.20 or later
Fixed in 3.5.14.20
Interim mitigation

Update all affected CODESYS V3 products to version v3.5.14.20 or later to patch the uncontrolled memory allocation vulnerability in the CmpGateway component.

Fix this in Control For Beaglebone Sl Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,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 $4,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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