Control For Beaglebone SlApplication · Codesys

CVE-2023-37558

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
After successful authentication as a user in multiple Codesys products in multiple versions, specific crafted network communication requests with inconsistent content can cause the CmpAppForce component to read internally from an invalid address, potentially leading to a denial-of-service condition. This vulnerability is different to CVE-2023-37559

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

This vulnerability in the CmpAppForce component of multiple Codesys products allows an authenticated attacker to send crafted network communication requests with inconsistent content, causing an invalid memory address read. This out-of-bounds read can trigger a denial-of-service condition.

MitigationApply vendor-supplied patches/updates for all affected Codesys products and versions. Since authentication is required, enforce strong credential policies and limit network access to trusted users only.

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 the Codesys Control product
    Determine which Codesys Control SL product is installed on the system (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi)
    Affected if The system is running any of the eight listed Codesys Control SL products
  2. Check the installed version
    Locate and read the version information for the Codesys Control installation, typically found in the product documentation, runtime environment, or system information panel
    Affected if The installed version is lower than 4.10.0.0
  3. Verify CmpAppForce component status
    Check if the CmpAppForce component is loaded or active in the Codesys runtime environment. This component handles forced variable operations and is part of the affected attack surface
    Affected if CmpAppForce is present and loaded in the runtime
  4. Assess network exposure
    Determine if the Codesys runtime network communication service is accessible from network segments. The vulnerability requires an authenticated attacker to send crafted requests
    Affected if The Codesys network service is accessible to untrusted users or network segments without proper access controls

The environment is affected if running any of the eight Codesys Control SL products at a version below 4.10.0.0 with the CmpAppForce component active and network accessibility to untrusted users.

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/updates for all affected Codesys products and versions. Since authentication is required, enforce strong credential policies and limit network access to trusted users only.

Recommended fix High confidence

Codesys Control for SL version 4.10.0.0 or later (specific to each platform: Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, Raspberry Pi)

  1. 1. Identify the specific Codesys Control product in use from the affected list (Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi)
  2. 2. Obtain the latest version of the respective Codesys Control for SL product from the official vendor
  3. 3. Plan an upgrade window following change management procedures
  4. 4. Perform a full backup of the current project, configurations, and runtime settings
  5. 5. Upgrade the Codesys Control for SL installation to version 4.10.0.0 or later
  6. 6. Verify the runtime starts successfully after upgrade
  7. 7. Test critical control functions to ensure normal operation
  8. 8. Confirm the CmpAppForce component responds correctly to network requests
Caveat No explicit breaking changes documented in provided materials; standard upgrade testing recommended

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-37558 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