CVE-2022-47390
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 multiple CODESYS products, allowing authenticated remote attackers to write data beyond stack boundaries. This can lead to denial of service, memory corruption, or potentially 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 Control product installedDetermine which CODESYS Control for...SL product is running on the device (e.g., Raspberry Pi, Beaglebone, Linux, PFC100, PFC200, IoT2000, Empc A/imx6, or Plcnext). This may be visible in the product name, system documentation, or runtime configuration.Affected if The device is running any of the eight listed CODESYS Control SL products.
-
Determine the installed CODESYS runtime versionLocate the runtime version information for the installed CODESYS Control product. This is typically found in the runtime system information, control panel, or version dialog of the CODESYS installation or runtime package.Affected if The installed version is lower than 4.8.0.0 for any of the affected CODESYS Control SL products.
-
Verify CmpTraceMgr component is loadedCheck if the CmpTraceMgr component is present and active in the CODESYS runtime. This may be visible in the runtime component list, diagnostic logs, or configuration file showing loaded components.Affected if CmpTraceMgr is loaded and active in the CODESYS runtime environment.
The environment is affected if it runs any of the eight listed CODESYS Control SL products with a version lower than 4.8.0.0 and has the CmpTraceMgr component loaded.
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 for affected CODESYS versions; restrict network access to minimize attack surface; ensure only authorized users have authentication credentials.
CODESYS Control products version 4.8.0.0 or later (e.g., Control For Linux 4.8.0.0, Control For Raspberry Pi 4.8.0.0, etc.)
- Identify the specific CODESYS Control product (e.g., Control for Linux, Control for Raspberry Pi, etc.) currently installed
- Determine the current installed version by checking the product documentation or system information
- Navigate to the official CODESYS download portal at https://www.codesys.com/ or contact your CODESYS support channel
- Download the updated CODESYS Control package for your specific product that includes version 4.8.0.0 or later
- Backup the current configuration and project files before applying the update
- Follow the vendor's official installation and upgrade instructions to apply the version 4.8.0.0 update
- Verify the update was successful by confirming the new version number
- Restart the CODESYS Control service if required by the update process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47390 — 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-47390 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