CVE-2023-37558
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 · uneditedAfter 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 confidenceThis 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.
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< 4.10.0.0< 4.10.0.0< 4.10.0.0< 4.10.0.0< 4.10.0.0< 4.10.0.0< 4.10.0.0< 4.10.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Codesys Control productDetermine 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
-
Check the installed versionLocate and read the version information for the Codesys Control installation, typically found in the product documentation, runtime environment, or system information panelAffected if The installed version is lower than 4.10.0.0
-
Verify CmpAppForce component statusCheck 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 surfaceAffected if CmpAppForce is present and loaded in the runtime
-
Assess network exposureDetermine if the Codesys runtime network communication service is accessible from network segments. The vulnerability requires an authenticated attacker to send crafted requestsAffected 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.
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 · scoped4.10.0.0
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.
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. 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. Obtain the latest version of the respective Codesys Control for SL product from the official vendor
- 3. Plan an upgrade window following change management procedures
- 4. Perform a full backup of the current project, configurations, and runtime settings
- 5. Upgrade the Codesys Control for SL installation to version 4.10.0.0 or later
- 6. Verify the runtime starts successfully after upgrade
- 7. Test critical control functions to ensure normal operation
- 8. Confirm the CmpAppForce component responds correctly to network requests
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-37558 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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