dbcve.org
Control For Beaglebone SlApplication · Codesys

CVE-2022-47388

HIGH · 8.8 CVSS v3.1 Published 2023-05-15
Fix available
A fix is available. Upgrade to 4.8.0.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
An authenticated, remote attacker may use a stack based out-of-bounds write vulnerability in the CmpTraceMgr Component of multiple CODESYS products in multiple versions to write data into the stack which can lead to a denial-of-service condition, memory overwriting, or remote code execution.

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 confidence

CVE-2022-47388 is a stack-based buffer overflow vulnerability in the CmpTraceMgr component of CODESYS products. An authenticated, remote attacker can exploit this to write data beyond stack boundaries, potentially achieving remote code execution, memory corruption, or causing denial of service.

MitigationApply vendor-provided security patches for affected CODESYS products and versions. Restrict network access to systems running CmpTraceMgr and enforce strong authentication to reduce attack surface.

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
Control For Beaglebone SlApplication
Affected:< 4.8.0.0
Control For Empc A\/imx6 SlApplication
Affected:< 4.8.0.0
Control For Iot2000 SlApplication
Affected:< 4.8.0.0
Control For Linux SlApplication
Affected:< 4.8.0.0
Control For Pfc100 SlApplication
Affected:< 4.8.0.0
Control For Pfc200 SlApplication
Affected:< 4.8.0.0
Control For Plcnext SlApplication
Affected:< 4.8.0.0
Control For Raspberry Pi SlApplication
Affected:< 4.8.0.0

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed CODESYS Control product
    Locate the CODESYS Control runtime package on the system and determine which variant is installed (Beaglebone, Empc A/imx6, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi)
    Affected if The system has any CODESYS Control 'SL' variant installed from the affected product list
  2. Determine the installed CODESYS version
    Use the system's package manager or check the CODESYS runtime information (typically via control runtime version command or package listing) to obtain the exact version number
    Affected if The installed version is lower than 4.8.0.0 for any of the affected product variants
  3. Verify CmpTraceMgr component is active
    Check the CODESYS runtime configuration or component list to determine if the CmpTraceMgr component is loaded or enabled on the system
    Affected if CmpTraceMgr component is present and active in the runtime environment

The system 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.8.0.0 AND has the CmpTraceMgr component enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.8.0.0 or later
Fixed in 4.8.0.0
Interim mitigation

Apply vendor-provided security patches for affected CODESYS products and versions. Restrict network access to systems running CmpTraceMgr and enforce strong authentication to reduce attack surface.

Recommended fix High confidence

Upgrade to CODESYS Control products version 4.8.0.0 or later for all affected platforms (Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, Raspberry Pi)

  1. Identify the specific CODESYS Control product (e.g., Control for Raspberry Pi, Control for Linux, etc.) currently installed
  2. Access the CODESYS update repository or customer portal at customers.codesys.com
  3. Locate and download the version 4.8.0.0 or later package for your specific product
  4. Backup the current project files and configuration before proceeding with the upgrade
  5. Install the updated CODESYS Control product version 4.8.0.0 or later
  6. Verify the CmpTraceMgr Component has been updated by checking the component version after installation
  7. Test the installation in a non-production environment before deploying to production
Caveat Review the 4.8.0.0 release notes for any API or configuration changes that may affect existing projects; test thoroughly in development environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Control For Beaglebone Sl Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47388 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-47388 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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