CVE-2023-37547
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-37545, CVE-2023-37546, 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 confidenceThis vulnerability in Codesys CmpApp component allows an authenticated attacker to send crafted network packets with inconsistent content, causing an invalid memory read. This leads to a denial-of-service condition on the affected device.
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 installed Codesys Control productLocate the Codesys Control runtime on the system and determine which variant is running (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi). This is typically found in the system inventory, installed packages, or runtime configuration.Affected if The system is running any of the listed Codesys Control variants.
-
Check installed versionQuery the installed version of the Codesys Control runtime. This can be done via the runtime's version information, system logs, or product documentation. Common methods include checking the About dialog in the development environment or querying the runtime service.Affected if The installed version is lower than 4.10.0.0 for any of the affected products.
-
Verify CmpApp component is loadedCheck if the CmpApp component is part of the active Codesys runtime. This component is typically part of the standard Codesys Control runtime stack. Inspect the runtime configuration or loaded modules.Affected if CmpApp component is loaded and active in the runtime environment.
-
Assess network exposureDetermine if the system has network services enabled for Codesys communication. Check if ports used by Codesys (typically 1217, 2455, or other CODESYS-related ports) are listening and accessible from the network.Affected if Network services are exposed and accessible to untrusted networks.
-
Review authentication configurationCheck the authentication settings for the Codesys Control runtime. Determine if user authentication is enabled and whether anonymous or default credentials are in use.Affected if Authentication is enabled but accessible to untrusted users, or weak authentication is configured.
The environment is affected if it runs any Codesys Control variant (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi) with a version lower than 4.10.0.0 and has the CmpApp component active with network exposure and authentication access.
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 patches from Codesys for all affected product versions. If patches are unavailable, implement network segmentation and restrict authentication access to minimize attack surface.
Upgrade to version 4.10.0.0 or later for the respective Control For SL product
- Identify the specific Codesys Control for product in use (Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi)
- Locate the current installed version of the Control for SL product
- Download the updated version 4.10.0.0 or later from the official Codesys vendor source (cert.vde.com or codesys.com)
- Follow the vendor's standard upgrade procedure for the specific Control for SL product
- Restart the service after applying the update
- Verify the new version is correctly installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37547 — 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-37547 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