CVE-2023-37555
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 versions of multiple Codesys products, after successful authentication as a user, specific crafted network communication requests with inconsistent content can cause the CmpAppBP component to read internally from an invalid address, potentially leading to a denial-of-service condition. This vulnerability is different to CVE-2023-37552, CVE-2023-37553, CVE-2023-37554 and CVE-2023-37556.
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 exists in the CmpAppBP component of multiple Codesys products. After successful user authentication, specially crafted network communication requests containing inconsistent content cause the component to attempt reading from an invalid memory address, potentially triggering 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 installed Codesys Control productsCheck the system for any Codesys Control runtime installations. Look for processes named 'CodesysControl' or check the installed packages on the device (common locations: /opt/codesys, /etc/Codesys, or check the Codesys Gateway/Sigma services).Affected if Any of these products are present: Codesys Control for Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, Plcnext, or Raspberry Pi.
-
Check Codesys Control runtime versionQuery the runtime version through the Codesys Gateway, typically via the Codesys Development Environment under 'Online' -> 'Device Update' or by checking the runtime version via the web interface if available, or using command 'codesysinfo --version' if installed.Affected if The installed version is below 4.10.0.0.
-
Verify CmpAppBP component is presentThe CmpAppBP component is part of the standard Codesys runtime. Check if the component is loaded by reviewing the runtime configuration files or logs, typically found in the runtime installation directory under /config or in system logs.Affected if The CmpAppBP component is loaded and active in the runtime.
-
Confirm network exposure of Codesys runtimeVerify if the Codesys runtime is accessible over the network by checking open ports (default Codesys ports: 11740, 1217, 1740, 1741) and reviewing network configuration to determine if unauthenticated or authenticated network access is possible.Affected if The Codesys runtime network interface is exposed to network attackers.
You are affected if you have any of the listed Codesys Control products installed with a version below 4.10.0.0, the CmpAppBP component is active, and the runtime is network-accessible to authenticated attackers.
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/updates from Codesys for affected product versions. Network segmentation and access controls can limit exposure to authenticated attackers.
4.10.0.0
- Upgrade CODESYS Control for the specific device (Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi) to version 4.10.0.0 or later
- Obtain the update from the official CODESYS download center or your device manufacturer's software distribution channel
- Before deployment, review the CODESYS version 4.10.0.0 release notes for any specific migration requirements
- Test the upgrade in a non-production environment to verify compatibility with your application
- After successful testing, deploy the update to production systems
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37555 — 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-37555 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