CVE-2023-37548
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, specific crafted network communication requests with inconsistent content can cause the CmpApp component to read internally from an invalid address, potentially leading to a denial-of-service condition. This vulnerability is different to CVE-2023-37545, CVE-2023-37546, CVE-2023-37547, CVE-2023-37549 and CVE-2023-37550
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 authentication-required vulnerability in multiple Codesys products where the CmpApp component reads from an invalid memory address when processing specially crafted network communication requests with inconsistent content after successful user authentication, potentially 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 Codesys Control product installedCheck the system or application documentation, or run 'codesyscontrol --version' or check the installed package name to determine which Codesys Control SL variant is in use (e.g., Raspberry Pi SL, Linux SL, Beaglebone SL, etc.)Affected if The product is any of the affected Codesys Control SL variants: Beaglebone, Empc A/imx6, IoT2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi
-
Determine the installed Codesys Control versionRun 'codesyscontrol --version' or check the package version via the system's package manager (dpkg -l codesyscontrol, rpm -qi codesyscontrol, etc.)Affected if The installed version is lower than 4.10.0.0
-
Verify CmpApp component is loadedCheck if the Codesys runtime process is running and the CmpApp component is loaded. On Linux, run 'ps aux | grep codesys' and look for the runtime process, or check the product-specific runtime logs for component initialization messages mentioning 'CmpApp'Affected if The CmpApp component is active and processing network requests
-
Check for crash or DoS indicatorsExamine system logs (/var/log/syslog, /var/log/messages) and Codesys runtime logs for crash reports, segfaults, or unexpected process termination events occurring after authenticated network communicationAffected if Crashes or DoS events coincide with authenticated network requests to the CmpApp component
-
Review network exposure and authentication logsCheck network configuration to confirm the Codesys runtime is exposed to network access, and review authentication logs for successful user logins followed by anomalous network communication activityAffected if The system accepts authenticated network connections and shows successful authentication events
The environment is affected if it runs any Codesys Control SL variant (Beaglebone, Empc A/imx6, IoT2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi) with version lower than 4.10.0.0, where the CmpApp component processes authenticated network requests.
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 security patches for affected Codesys products when available; until then, restrict network access to trusted authenticated users and monitor for DoS indicators.
Upgrade to Codesys Control version 4.10.0.0 or later
- Identify the current installed version of the affected Codesys Control product
- Download Codesys Control version 4.10.0.0 or later from the official Codesys download portal or your vendor's software distribution channel
- Before upgrading, backup all existing projects, configurations, and runtime settings
- Stop any running Codesys Control runtime services on the target device
- Install the new version (4.10.0.0 or later) following the vendor's standard installation procedure
- Restart the Codesys Control runtime services
- Verify the installation was successful and the runtime is functioning properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37548 — 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-37548 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