CVE-2022-47385
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 CmpAppForce 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 confidenceThis is a stack-based buffer overflow (out-of-bounds write) vulnerability in the CmpAppForce Component of CODESYS products. An authenticated remote attacker can write data beyond the intended 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 Control product installedDetermine which CODESYS Control variant is running on the system (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi)Affected if The system is running any of the listed CODESYS Control products without knowing the version
-
Check the installed CODESYS Control versionLocate and inspect the CODESYS Control version information, typically found in the product documentation, control runtime files, or system information panel. Compare the version number against the affected range of < 4.8.0.0Affected if The installed version is lower than 4.8.0.0 (for example, 4.7.x, 4.6.x, or earlier)
-
Verify the CmpAppForce Component is presentCheck if the CmpAppForce Component is loaded in the CODESYS runtime. This may be visible in the runtime component list, system logs, or configuration files if the component is actively loadedAffected if The CmpAppForce Component is loaded and active in the CODESYS runtime environment
-
Confirm network exposure of the CODESYS runtimeReview network configuration settings to determine if the CODESYS runtime is accessible over the network. This typically involves checking network interface bindings, port configurations, or firewall rules for ports used by CODESYSAffected if The CODESYS Control runtime is exposed to the network without proper segmentation or access controls
A system is affected if it runs any CODESYS Control variant (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi) with version lower than 4.8.0.0 and has the CmpAppForce component accessible over the network.
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-provided patches for affected CODESYS products; if patches are unavailable, implement network segmentation to limit exposure and enforce strong authentication controls to reduce the attack surface.
CODESYS Control products version 4.8.0.0 or later
- 1. Identify the specific CODESYS Control product in use (e.g., Control for Linux, Control for Raspberry Pi, etc.)
- 2. Obtain the CODESYS installation or firmware package for version 4.8.0.0 or later from the official CODESYS download channels
- 3. Before applying the upgrade, ensure all current projects are backed up
- 4. Apply the upgrade following the product-specific installation instructions provided in the CODESYS documentation
- 5. After upgrade, verify that the CmpAppForce component is functioning correctly and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47385 — 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-47385 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