CVE-2023-37545
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 · uneditedIn 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-37546, CVE-2023-37547, CVE-2023-37548, CVE-2023-37549, 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 confidenceThis is a denial-of-service vulnerability in multiple Codesys products where authenticated users can send crafted network communication requests with inconsistent content, causing the CmpApp component to read from an invalid memory address. The attack requires successful authentication first, then exploits improper input handling during network request processing.
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 installed Codesys Control productCheck the product name by inspecting the Codesys runtime installation or system information. On the device, look for codesyscontrol or similar runtime process names, or check the project file (.project) if you have access to the development environment.Affected if The product is one of the eight affected SL variants (Beaglebone, Empc A/imx6, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi).
-
Determine the installed version numberAccess the Codesys runtime version through the Codesys Development System by connecting to the target device and checking the 'Device Information' or 'Online' -> 'Device Info'. Alternatively, check the runtime package version file on the device itself if accessible via SSH or file system.Affected if The version is lower than 4.10.0.0 (for example, 3.5.x, 4.0.x, 4.1.x, etc.).
-
Verify network accessibility of the Codesys runtimeCheck if the Codesys network ports (typically 1217/tcp for the Codesys Gateway, 11740/tcp for runtime communication) are exposed to untrusted networks. Use 'netstat -an' or 'ss -tuln' on the device to list listening ports.Affected if The Codesys runtime ports are accessible from networks where untrusted or unknown users could connect.
-
Confirm authentication is in useReview the Codesys runtime settings to confirm that user authentication is enabled and configured. Check the 'User Management' settings in the Codesys Development System or examine the runtime configuration file (typically CmpAuthenticate settings).Affected if Authentication is disabled or uses weak/default credentials, as the vulnerability requires an authenticated user session.
You are affected if you are running any of the eight Codesys Control SL variants (Beaglebone, Empc A/imx6, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi) with a version number below 4.10.0.0, and your device is network-accessible with authentication configured.
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-provided patches when available. Until then, implement network segmentation to limit access to Codesys devices to authorized personnel only, and consider rate-limiting or monitoring for anomalous network requests.
4.10.0.0 or later
- Identify the specific Codesys Control product in use (e.g., Control for Raspberry Pi, Control for Linux, etc.)
- Locate the current installed version of the Control for [product] software
- Download the version 4.10.0.0 or later of the affected Control for [product] from the official vendor source (cert.vde.com or official Codesys distribution)
- Ensure all runtime environments and projects are backed up before upgrading
- Install the updated Control for [product] version 4.10.0.0 or later following standard vendor upgrade procedures
- Restart the runtime service to ensure the new component version is loaded
- Verify the CmpApp component is running without errors and the service is stable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37545 — 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-37545 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