CVE-2023-37554
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-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 · high 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 CmpAppBP component to read from an invalid memory address, potentially crashing the service.
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 productCheck system information or installed packages to determine which Codesys Control variant is running (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi)Affected if The system runs any of the listed Codesys Control products
-
Determine Codesys Control versionUse the product's version lookup mechanism (such as checking the About section in the development environment, examining the installed package version, or querying the runtime system) to obtain the exact version numberAffected if The installed version is lower than 4.10.0.0
-
Verify CmpAppBP component presenceInspect the Codesys installation or runtime configuration files for the CmpAppBP component. This component is typically part of the application build process and may appear in project files or runtime logsAffected if CmpAppBP component is present in the installation or project configuration
-
Confirm network communication is enabledCheck the Codesys runtime configuration or network settings to verify that network communication ports and protocols are active (typically ports 11740 or 1217 for Codesys communication)Affected if Network communication is enabled and accessible
-
Assess network exposureReview firewall rules, network access controls, or VLAN configuration to determine if the Codesys network interface is exposed beyond the intended trusted networkAffected if The Codesys runtime network interface is accessible to untrusted users or networks
A system is affected if it runs any of the listed Codesys Control products at a version lower than 4.10.0.0 with CmpAppBP component and has network communication enabled.
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 all affected Codesys product versions and implement network segmentation to limit access to authenticated users only.
4.10.0.0 or later
- Identify the specific Codesys Control product (e.g., Control for Linux, Control for Raspberry Pi, etc.) currently deployed
- Check the current installed version of the affected Codesys Control product
- Obtain the fixed version (4.10.0.0 or later) from the official Codesys download sources or your existing vendor agreement/channel
- Follow the standard Codesys product upgrade procedure for your specific platform - this typically involves stopping the runtime, replacing the software package, and restarting the runtime
- After upgrade, verify the CmpAppBP component is functioning properly and the service is operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37554 — 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-37554 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