CVE-2023-37553
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-37554, CVE-2023-37555 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 is an out-of-bounds read vulnerability in the CmpAppBP component of multiple Codesys products. An authenticated attacker can send crafted network communication requests with inconsistent content to trigger the component to read from an invalid memory address, causing 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 productLocate the specific Codesys Control runtime installed on the system. Check product name (Beaglebone, Empc A/imx6, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi) either in installed packages, program files, or system information.Affected if The system runs any of these eight Codesys Control products: Beaglebone SL, Empc A/imx6 SL, IoT2000 SL, Linux SL, PFC100 SL, PFC200 SL, PLCnext SL, or Raspberry Pi SL.
-
Check installed Codesys versionQuery the installed version of the Codesys Control runtime. This can typically be done via the product's system info, registry entries, or by running 'codesyscontrol --version' if available. Compare the version number against the affected range.Affected if The installed version is lower than 4.10.0.0 (any version 3.x or 4.x.x.x below 4.10.0.0).
-
Verify CmpAppBP component presenceCheck if the CmpAppBP component is loaded or active in the Codesys runtime. This may be visible in the runtime's component list, log files, or diagnostic output.Affected if The CmpmpBP component is present and loaded in the Codesys runtime environment.
-
Assess network accessibilityReview network configuration to determine if the Codesys runtime network ports are exposed to untrusted networks. Check firewall rules and network ACLs surrounding the device.Affected if The Codesys Control runtime is accessible over the network from untrusted or external IP addresses.
-
Review authentication configurationExamine the Codesys runtime authentication settings to confirm whether user authentication is enabled for network communication requests.Affected if Authentication is disabled or uses default credentials, allowing unauthenticated network access to the runtime.
A system is affected if it runs any of the eight listed Codesys Control products with a version lower than 4.10.0.0 and has the CmpAppBP component active, especially when accessible over a network without proper access controls.
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 for affected Codesys product versions. Since authentication is required, restrict network access to trusted users and monitor for anomalous requests.
CODESYS Control products version 4.10.0.0
- 1. Identify all affected Codesys Control products (Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, Raspberry Pi) currently running versions prior to 4.10.0.0
- 2. Create a backup of the current project configurations and applications running on affected devices
- 3. Download the CODESYS Control product version 4.10.0.0 or later from the official Codesys download area (shop.codesys.com) or your vendor-specific update channel
- 4. Review release notes for version 4.10.0.0 to confirm the vulnerability fix and check for any product-specific installation requirements
- 5. Install version 4.10.0.0 on each affected device following the vendor's installation instructions
- 6. After installation, verify that the CmpAppBP component is running without errors
- 7. Test that network communication functions normally after the upgrade
- 8. Monitor the system for any residual issues and verify the CVE-2023-37553 vulnerability is no longer present
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-37553 — 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-37553 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