CVE-2023-37552
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-37553, 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 vulnerability in Codesys CmpAppBP component allows authenticated attackers to trigger an invalid memory read by sending specially crafted network packets with inconsistent content. This causes a denial-of-service condition due to the invalid address access.
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 device. Check system information, installed packages, or runtime documentation for the specific product name (e.g., Codesys Control for Raspberry Pi SL, Codesys Control for Linux SL).Affected if The product matches one of the affected variants listed in the CVE (Beaglebone, Empc A/imx6, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi).
-
Check Codesys Control runtime versionRun the appropriate command or check the runtime configuration to retrieve the installed version. For Linux-based systems, this may be in /etc/, a service banner, or the runtime's About/Version information. Compare the version number to 4.10.0.0.Affected if The installed version is less than 4.10.0.0 for any affected product variant.
-
Verify CmpAppBP component is in useCheck if the CmpAppBP component is loaded or referenced in the Codesys runtime environment. This may be visible in runtime logs, component lists, or the project's library/framework dependencies.Affected if The CmpAppBP component is present and active in the runtime environment.
-
Assess network exposure of Codesys runtimeDetermine if the Codesys Control runtime is bound to network interfaces accessible from outside the local network. Check firewall rules, network bindings, or service configuration for the runtime's communication ports.Affected if The runtime accepts network connections from untrusted or external network segments.
A user is affected if they run any of the listed Codesys Control products with a version below 4.10.0.0 where 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 security updates for affected Codesys products. If patches are unavailable, network segmentation and restricting authentication access can reduce attack surface.
CODESYS Control version 4.10.0.0 or later for all affected product variants
- 1. Identify the currently installed CODESYS Control product version by checking the runtime or project properties
- 2. Create a full backup of the current project and runtime configuration
- 3. Download CODESYS Control version 4.10.0.0 or later from the official CODESYS download area (download.codesys.com)
- 4. Stop any running CODESYS Control runtime services on the target device
- 5. Install the updated CODESYS Control package following the vendor's installation instructions
- 6. Restart the CODESES Control runtime services
- 7. Verify the installed version shows 4.10.0.0 or higher to confirm the patch was applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37552 — 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-37552 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