CVE-2022-47389
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 · uneditedAn 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 confidenceA stack-based out-of-bounds write vulnerability exists in the CmpTraceMgr component of CODESYS products. An authenticated remote attacker can exploit this to write data beyond stack boundaries, potentially causing denial of service, memory corruption, or achieving remote code execution.
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.8.0.0< 4.8.0.0< 4.8.0.0< 4.8.0.0< 4.8.0.0< 4.8.0.0< 4.8.0.0< 4.8.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify CODESYS Control product variantCheck which CODESYS Control runtime is installed on the system. Common locations: /etc/codesys or C:\Program Files\CODESYS on Windows. Look for product-specific folders (e.g., 'CODESYS Control for Raspberry Pi SL', 'CODESYS Control for Linux SL').Affected if The product name matches one of the affected variants: Beaglebone, Empc A/imx6, IoT2000, Linux, PFC100, PFC200, Plcnext, or Raspberry Pi.
-
Determine installed CODESYS runtime versionCheck the runtime version via the CODESYS Development System (Project > Show Device) or by inspecting the product-specific version file. For Linux-based systems, check /etc/codesys versions or the product-specific version info. On Windows, check 'C:\Program Files\CODESYS\<Product>\VERSION.txt' or similar.Affected if The installed version is lower than 4.8.0.0 for any of the listed product variants.
-
Verify CmpTraceMgr component is loadedInspect the CODESYS configuration file (CODESYSControl.cfg) for entries enabling CmpTraceMgr, or check runtime logs for traces of the Trace Manager component initialization during startup.Affected if The CmpTraceMgr component is present and loaded in the runtime configuration.
-
Check network exposure and authenticationReview network firewall rules and CODESYS runtime network settings. Verify that remote connections require authentication and that the PLC is not directly exposed to untrusted networks.Affected if The runtime is accessible over network without proper authentication controls or is exposed to untrusted networks.
A user is affected if they run any CODESYS Control product variant (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, Plcnext, or Raspberry Pi SL) with version below 4.8.0.0 and have the CmpTraceMgr component enabled and network-accessible.
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.8.0.0
Apply vendor patches or updates for affected CODESYS products. Restrict network access to trusted personnel and enforce strong authentication to reduce attack surface.
4.8.0.0
- Identify the specific CODESYS Control product (e.g., Control For Raspberry Pi Sl, Control For Linux Sl, etc.) from the affected products list
- Check the current installed version of the CODESYS Control product on the target device/system
- Access the CODESYS customer portal at customers.codesys.com and navigate to the downloads or patches section
- Locate and download the updated CODESYS Control product version 4.8.0.0 or later for your specific platform
- Before applying the update, create a complete backup of the current system configuration and any running applications
- Install the updated version 4.8.0.0 following the standard CODESYS installation procedures for your platform
- After installation, verify that the CmpTraceMgr Component has been updated and the vulnerability is resolved
- Test the system to ensure normal operation and that the out-of-bounds write vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47389 — 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-2022-47389 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