CVE-2022-47386
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 · high confidenceA stack-based buffer overflow vulnerability exists in the CmpTraceMgr component of multiple 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 the CODESYS product installedCheck the product name via the system package manager, CODESYS runtime information file, or runtime configuration (commonly found in /etc/codesys* or /opt/codesys* directories)Affected if The product matches one of the affected variants: Beaglebone, Empc A/imx6, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi SL versions before 4.8.0.0
-
Determine the installed CODESYS runtime versionRun 'codesysinfo --version' or check the runtime package version via the package manager (dpkg/rpm), or inspect the CODESYS Control runtime binary version informationAffected if The version number is lower than 4.8.0.0 for the identified product
-
Verify the CmpTraceMgr component is presentCheck the CODESYS configuration file (CODESYSControl.cfg) for the CmpTraceMgr component registration, or query the runtime via the CODESYS Development System if the component is loaded at runtimeAffected if The CmpTraceMgr component is loaded or configured in the CODESYS runtime
-
Check network exposure and authentication statusInspect the CODESYS network configuration (CODESYSControl.cfg) for exposed network interfaces and verify that authentication is properly configured and enforcedAffected if The runtime is accessible over the network without proper authentication or uses default/weak credentials
You are affected if you are running any of the listed CODESYS Control SL products with a version below 4.8.0.0 and the CmpTraceMgr component is loaded in your environment.
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-supplied patches from CODESYS for all affected product versions. Until patches are available, restrict network access to affected systems and enforce strict authentication controls.
CODESYS Control version 4.8.0.0 or later (for your specific platform: Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi)
- Identify the specific CODESYS Control for <product> installation in your environment
- Locate the current version of the installed CODESYS Control runtime
- Download the CODESYS Control version 4.8.0.0 or later from the official CODESYS download repository (store.codesys.com) or your licensed customer portal
- Review the release notes for version 4.8.0.0 to confirm the CmpTraceMgr Component vulnerability (CVE-2022-47386) is addressed
- Backup the current project files, PLC configurations, and runtime settings before performing the upgrade
- Stop all running CODESYS Control runtime services on the target device
- Install the new CODESYS Control version 4.8.0.0 or later following the vendor's installation instructions
- Restart the CODESYS Control runtime services
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.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 $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47386 — 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-47386 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