dbcve.org
Control For Beaglebone SlApplication · Codesys

CVE-2019-9013

HIGH · 8.8 CVSS v3.1 Published 2019-08-15
Fix available
A fix is available. Upgrade to 3.5.16.0 or later.
See remediation →
93/100
Remediation priority · Urgent
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 application may utilize non-TLS based encryption, which results in user credentials being insufficiently protected during transport. All variants of the following CODESYS V3 products in all versions containing the CmpUserMgr 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 RTE V3, CODESYS Control RTE V3 (for Beckhoff CX), CODESYS Control Win V3 (also part of the CODESYS Development System setup), CODESYS V3 Simulation Runtime (part of the CODESYS Development System), CODESYS Control V3 Runtime System Toolkit, CODESYS HMI V3.

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 V3 runtime products use non-TLS based encryption for user credential transport, causing passwords and authentication data to be transmitted without adequate protection. This allows network eavesdropping or man-in-the-middle attackers to intercept and capture valid user credentials.

MitigationEnable TLS/SSL encryption for all CODESYS communications where available, or apply vendor-provided patches to affected CODESYS V3 products. Network segmentation can reduce exposure risk until proper remediation is applied.

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.16.0
Control For Empc A\/imx6 SlApplication
Affected:>= 3.0, < 3.5.16.0
Control For Iot2000 SlApplication
Affected:>= 3.0, < 3.5.16.0
Control For Linux SlApplication
Affected:>= 3.0, < 3.5.16.0
Control For Pfc100 SlApplication
Affected:>= 3.0, < 3.5.16.0
Control For Pfc200 SlApplication
Affected:>= 3.0, < 3.5.16.0
Control Rte SlApplication
Affected:>= 3.0, < 3.5.16.0
Control Win SlApplication
Affected:>= 3.0, < 3.5.16.0

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

CVSS:3.1/AV:A/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 V3 runtime product
    Check system for presence of CODESYS Control components. Common locations: /opt/codesys, /usr/local/codesys, or check installed packages. Look for product names: Codesys Control For Beaglebone, Empc, IoT2000, Linux, Pfc100, Pfc200, Rte, or Win.
    Affected if Any of these CODESYS Control products are found on the system
  2. Determine installed CODESYS version
    Check the installed version of the CODESYS runtime. Common methods: (1) Look at the product-specific version file in the installation directory, (2) Check the package manager for installed codesys packages, (3) Query the runtime directly if accessible via management interface.
    Affected if Installed version is >= 3.0 and < 3.5.16.0
  3. Verify credential transport configuration
    Examine CODESYS configuration files for user authentication settings. Check files like CmpSettings, webvisu configuration, or the PLC's runtime settings for whether TLS/SSL is enabled for user credential transport. Look for settings related to authentication encryption or secure communication.
    Affected if Credential transport is configured without TLS/SSL encryption (plaintext or weakly encrypted authentication)
  4. Check network communication settings
    Inspect CODESYS runtime network configuration files (such as gateway settings or plc configuration) to determine if secure communication channels are enforced for login and authentication operations.
    Affected if Network communications allow unencrypted credential transmission

A system is affected if it runs any CODESYS V3 runtime product (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, RTE, or Win) with version 3.0 to less than 3.5.16.0 AND uses non-TLS credential transport.

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.16.0 or later
Fixed in 3.5.16.0
Interim mitigation

Enable TLS/SSL encryption for all CODESYS communications where available, or apply vendor-provided patches to affected CODESYS V3 products. Network segmentation can reduce exposure risk until proper remediation is applied.

Fix this in Control For Beaglebone Sl Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
60.0 hours of engineering $10,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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