dbcve.org
Control For Beaglebone SlApplication · Codesys

CVE-2022-47384

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 · moderate confidence

A stack-based out-of-bounds write vulnerability in the CmpTraceMgr Component of CODESYS products allows an authenticated remote attacker to write data beyond stack boundaries, potentially causing denial of service, memory corruption, or achieving remote code execution.

MitigationApply vendor-provided security patches or updates for affected CODESYS products, and enforce strict network access controls to limit exposure to authenticated attackers.

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 CODESYS Control product
    Check system information or look for CODESYS Control runtime processes (e.g., codesyscontrol, CmpTraceMgr related services)
    Affected if The system runs any of the listed CODESYS Control products (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, PLCnext, Raspberry Pi)
  2. Determine installed CODESYS version
    Use the CODESYS development environment or check the runtime version via system commands or configuration files (typically in /etc/codesys or the product's installation directory)
    Affected if Installed version is lower than 4.8.0.0 for any of the affected product variants
  3. Verify CmpTraceMgr Component is present
    Check if the CmpTraceMgr component is loaded in the CODESYS runtime - this may be visible in runtime configuration files or component listings
    Affected if CmpTraceMgr component is present and active in the CODESYS runtime
  4. Assess network accessibility
    Review network configuration and firewall rules to determine if the CODESYS runtime management ports are exposed to untrusted networks
    Affected if CODESYS runtime ports (typically 1217, 1743, or similar) are accessible from untrusted or external networks

A system is affected if it runs any of the listed CODESYS Control products with version below 4.8.0.0 and has the CmpTraceMgr component enabled with network exposure to potential authenticated attackers.

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 or updates for affected CODESYS products, and enforce strict network access controls to limit exposure to authenticated attackers.

Recommended fix Moderate confidence

CODESYS Control products version 4.8.0.0 or later

  1. 1. Identify all affected CODESYS Control devices in the environment (Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, Raspberry Pi).
  2. 2. Document the current firmware/software version of each affected device.
  3. 3. Obtain the CODESYS Control software version 4.8.0.0 or later from the official CODESYS download repository (customers.codesys.com).
  4. 4. Review the CODESYS installation and upgrade documentation for your specific device platform.
  5. 5. Create a backup of the current device configuration and project files.
  6. 6. Upgrade each affected device to version 4.8.0.0 or later following the platform-specific upgrade procedure.
  7. 7. After upgrade, verify the CmpTraceMgr Component is updated and the vulnerability is resolved.
  8. 8. Test that normal control functionality operates correctly after the upgrade.
Caveat Before upgrading, review release notes for version 4.8.0.0 to confirm no breaking changes affect your specific device configuration or existing projects; test in a non-production environment first.

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

Fix this in Control For Beaglebone Sl Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47384 — 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-47384 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