CVE-2023-37551
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 Codesys products in multiple versions, after successful authentication as a user, specially crafted network communication requests can utilize the CmpApp component to download files with any file extensions to the controller. In contrast to the regular file download via CmpFileTransfer, no filtering of certain file types is performed here. As a result, the integrity of the CODESYS control runtime system may be compromised by the files loaded onto the controller.
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 integrity vulnerability in CODESYS control runtime products where the CmpApp component allows authenticated users to download files of any extension without the file type filtering that CmpFileTransfer enforces. This bypass enables potentially malicious files to be loaded onto the controller, compromising the runtime system's integrity.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 CODESYS Control runtime productLocate and identify which CODESYS Control runtime is installed on the device (Beaglebone, Empc, IoT2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi). Consult the system documentation or runtime installation to confirm the specific product name.Affected if The product is one of the eight affected CODESYS Control runtime products listed in the CVE.
-
Determine the installed versionCheck the installed version of the CODESYS Control runtime product. Compare it against the affected version range: versions prior to 4.10.0.0 are vulnerable.Affected if The installed version is lower than 4.10.0.0 for the affected product.
-
Verify CmpApp component statusInspect the CODESYS runtime configuration or component list to determine whether the CmpApp component is loaded and active. This component is required for the vulnerability to be exploitable.Affected if CmpApp is enabled and running on the system.
-
Assess network exposureReview network configuration and firewall rules to determine if the CODESYS runtime web interface or management ports are accessible from untrusted networks. The vulnerability requires an authenticated user to exploit the file download bypass.Affected if The runtime management interface is accessible from networks beyond the trusted operational environment.
You are affected if you are running any of the eight CODESYS Control runtime products (Beaglebone, Empc, IoT2000, Linux, Pfc100, Pfc200, Plcnext, Raspberry Pi) with a version lower than 4.10.0.0 and the CmpApp component is 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
Restrict network access to controllers using firewalls or network segmentation, implement monitoring for anomalous file transfers, and apply vendor patches when available. Consider disabling CmpApp if not required for the application.
CODESYS Control version 4.10.0.0 or later
- Identify the specific CODESYS Control for [product] variant currently installed
- Backup the controller configuration and project files
- Upgrade the CODESYS Control runtime to version 4.10.0.0 or later
- Verify the upgrade was successful by checking the runtime version
- Ensure network access controls remain in place even after patching
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-37551 — 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-37551 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