dbcve.org
Control For Beaglebone SlApplication · Codesys

CVE-2023-37546

MEDIUM · 6.5 CVSS v3.1 Published 2023-08-03
Fix available
A fix is available. Upgrade to 4.10.0.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
In multiple Codesys products in multiple versions, after successful authentication as a user, specific crafted network communication requests with inconsistent content can cause the CmpApp component to read internally from an invalid address, potentially leading to a denial-of-service condition. This vulnerability is different to CVE-2023-37545, CVE-2023-37547, CVE-2023-37548, CVE-2023-37549 and CVE-2023-37550

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 confidence

This is a memory access vulnerability in Codesys industrial control software products. After successful user authentication, a remote attacker can send specially crafted network packets with inconsistent content that cause the CmpApp component to read from an invalid memory address, resulting in potential denial of service. The attack requires authentication but can be exploited over the network.

MitigationApply vendor-supplied patches for affected Codesys products; restrict network access to control system interfaces to authenticated, authorized personnel only; implement network segmentation to limit exposure.

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:< 4.10.0.0
Control For Empc A\/imx6 SlApplication
Affected:< 4.10.0.0
Control For Iot2000 SlApplication
Affected:< 4.10.0.0
Control For Linux SlApplication
Affected:< 4.10.0.0
Control For Pfc100 SlApplication
Affected:< 4.10.0.0
Control For Pfc200 SlApplication
Affected:< 4.10.0.0
Control For Plcnext SlApplication
Affected:< 4.10.0.0
Control For Raspberry Pi SlApplication
Affected:< 4.10.0.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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Control product
    Locate the Codesys runtime installation by checking for directories such as /opt/codesys, /usr/local/codesys, or C:\Program Files\Codesys. Review product documentation or runtime configuration files for the specific Codesys Control variant (e.g., Raspberry Pi, Linux, Beaglebone).
    Affected if The system is running any of the following Codesys Control products: Beaglebone SL, Empc A/imx6 SL, IoT2000 SL, Linux SL, PFC100 SL, PFC200 SL, PLCnext SL, or Raspberry Pi SL.
  2. Determine installed version number
    Access the runtime management interface, check the product About/Version information within the Codesys Development System, or inspect the runtime package version file (typically found in the installation directory). Compare the version to 4.10.0.0.
    Affected if The installed version is lower than 4.10.0.0.
  3. Verify network communication is enabled
    Inspect the Codesys Control runtime network configuration settings. Check if the network adapter is bound and the CODESYS control runtime is listening on network ports (default ports 1217, 1740, 1741). Use netstat or equivalent to list active network listeners.
    Affected if The runtime has an active network listener and accepts remote connections.
  4. Confirm remote authentication is configured
    Review the user management and authentication settings in the Codesys Control runtime. Check whether remote users are defined or if the Webvisualization or remote PLC configurations permit authenticated access.
    Affected if Remote user authentication is enabled or remote access is permitted.

The environment is affected if any Codesys Control product (Beaglebone SL, Empc A/imx6 SL, IoT2000 SL, Linux SL, PFC100 SL, PFC200 SL, PLCnext SL, or Raspberry Pi SL) is running with a version lower than 4.10.0.0 and has network communication with remote authentication enabled.

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

Apply vendor-supplied patches for affected Codesys products; restrict network access to control system interfaces to authenticated, authorized personnel only; implement network segmentation to limit exposure.

Recommended fix High confidence

4.10.0.0 or later

  1. Identify the specific Codesys Control product (Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi) currently installed
  2. Upgrade the Codesys Control software to version 4.10.0.0 or later
  3. After upgrading, verify the CmpApp component is running correctly and the service is operational

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

Fix this in Control For Beaglebone Sl Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
28.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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