CVE-2023-37557
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 · uneditedAfter successful authentication as a user in multiple Codesys products in multiple versions, specific crafted remote communication requests can cause the CmpAppBP component to overwrite a heap-based buffer, which can lead to a denial-of-service condition.
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 confidenceA heap-based buffer overflow vulnerability in the CmpAppBP component of multiple Codesys products. After successful user authentication, specially crafted remote communication requests can overwrite heap memory, 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 the installed Codesys Control productDetermine which specific Codesys Control product is running on the system (e.g., Beaglebone, Raspberry Pi, Linux, PFC100, PFC200, IoT2000, Empc, Plcnext)Affected if The product is any of the affected variants listed in the CVE
-
Check the installed Codesys Control versionLocate and inspect the installed version of the Codesys Control productAffected if The installed version is lower than 4.10.0.0
-
Verify if remote communication is enabledInspect the product configuration for remote communication settings or network communication featuresAffected if Remote communication/network features are enabled and accessible to attackers
-
Confirm user authentication is configuredCheck the authentication configuration to determine if remote users can authenticate to the systemAffected if Remote user authentication is enabled, allowing authenticated attackers to exploit the flaw
-
Inspect network exposureReview network accessibility of the Codesys remote communication ports/servicesAffected if The system is directly accessible over a network to untrusted users or segments
The environment is affected if a Codesys Control product from the affected list is running with version lower than 4.10.0.0 and has remote communication enabled with user authentication configured.
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 products and enforce network segmentation to limit exposure to authenticated attackers.
Upgrade to Codesys Control products version 4.10.0.0 or later
- 1. Identify the specific Codesys Control product in use (e.g., Control for Linux, Control for Raspberry Pi, etc.)
- 2. Check the current installed version of the product
- 3. If the current version is below 4.10.0.0, plan for an upgrade to version 4.10.0.0 or later
- 4. Backup the current configuration before proceeding with the upgrade
- 5. Obtain the updated software package from the official Codesys download source (e.g., store.codesys.com or your specific vendor)
- 6. Install the new version (4.10.0.0 or higher) following the vendor's standard upgrade procedure
- 7. After installation, verify the CmpAppBP component is updated and the service restarts successfully
- 8. Test that remote communication requests work correctly after the upgrade
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-37557 — 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-37557 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