dbcve.org
Control For Beaglebone SlApplication · Codesys

CVE-2022-47383

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 buffer overflow vulnerability exists in the CmpTraceMgr component of CODESYS products. An authenticated attacker can exploit this out-of-bounds write to corrupt stack memory, potentially achieving remote code execution, or cause denial-of-service by crashing the application.

MitigationApply vendor-provided security updates/patches for affected CODESYS products. If patches are unavailable, network segmentation and limiting authentication access can 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 CODESYS Control product variant
    Determine which CODESYS Control SL product is installed on your system (Beaglebone, Empc A/imx6, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi)
    Affected if The installed product is one of the eight affected variants listed in the CVE
  2. Check installed CODESYS version
    Locate and retrieve the installed version of the CODESYS Control runtime package. This is typically shown in the product's system information, runtime logs, or control runtime configuration interface.
    Affected if The installed version is below 4.8.0.0 (for example, 4.7.x, 4.6.x, etc.)
  3. Verify CmpTraceMgr component presence
    Inspect the CODESYS runtime configuration or component list to confirm the CmpTraceMgr component is loaded and active on the system
    Affected if The CmpTraceMgr component is present and enabled in the runtime environment
  4. Confirm authentication access method
    Review system configuration to determine if remote authentication or external user access is enabled for the CODESYS runtime
    Affected if Remote or external authentication is enabled, allowing authenticated attackers to reach the vulnerable component

Your environment is affected if you are running any of the eight listed CODESYS Control SL product variants at version 4.8.0.0 or lower, with the CmpTraceMgr component active and authentication access configured.

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 updates/patches for affected CODESYS products. If patches are unavailable, network segmentation and limiting authentication access can reduce attack surface.

Recommended fix High confidence

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

  1. 1. Identify the specific CODESYS Control product variant (Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi) in use
  2. 2. Determine the currently installed version by checking the product documentation or system information
  3. 3. Download the CODESYS Control product version 4.8.0.0 or later from the official CODESYS download page (store.codesys.com) or the customer portal (customers.codesys.com)
  4. 4. Backup the current project files and configuration settings
  5. 5. Install version 4.8.0.0 of the affected CODESYS Control product following the product-specific installation instructions
  6. 6. Restore the project files and configuration settings after upgrade
  7. 7. Verify the installation was successful by checking the version number
  8. 8. Test the application functionality to ensure the upgrade did not break existing functionality
Caveat Check product-specific release notes for any breaking changes between your current version and 4.8.0.0

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

Fix this in Control For Beaglebone Sl Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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