CVE-2022-47381
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 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 confidenceAn authenticated remote attacker exploits a stack-based out-of-bounds write vulnerability in multiple CODESYS products to write data beyond stack boundaries. This can cause 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 installed CODESYS Control product variantCheck which CODESYS Control runtime is installed on the system. Common locations include /etc/codesys, /opt/codesys, or check the installed packages. Look for one of: Beaglebone, Empc A/imx6, IoT2000, Linux, PFC100, PFC200, PLCnext, Raspberry Pi.Affected if Any CODESYS Control SoftLogic runtime variant from the list is installed.
-
Locate the runtime version informationCheck the version of the installed CODESYS Control runtime. Common methods: (1) Look for a file like 'CODESYSControl.cfg' or version info in the installation directory, (2) If the runtime has a web interface (port 8080 or 8443), access it to view version info, (3) Check the package manager or installation logs for the version number.Affected if You cannot determine the version or the version file is missing.
-
Compare installed version against 4.8.0.0Extract the numeric version of the installed CODESYS Control runtime and compare it to 4.8.0.0. Versions below 4.8.0.0 are affected (e.g., 4.7.0.0, 4.6.0.0, 3.5.x). Note that version 4.8.0.0 itself and later are not affected.Affected if The installed version is less than 4.8.0.0 (e.g., 4.7.x, 4.6.x, or earlier).
-
Verify remote access is enabledConfirm whether the CODESYS Control runtime has network communication enabled and is accessible over Ethernet. Check if the runtime is bound to a network interface (not loopback only) and check for open ports typically used by CODESYS (e.g., 11740, 1217, 8080/8443 for web server).Affected if The runtime has network interfaces enabled and is reachable from the network.
-
Check for user accountsVerify if user accounts are configured in the CODESYS runtime. The vulnerability requires an authenticated attacker, so check if local user accounts, Windows domain accounts, or other authentication methods are enabled in the CODESYS Control configuration.Affected if User authentication is configured and network access to the runtime is possible.
The environment is affected if a CODESYS Control SoftLogic variant (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi) is installed with a version number lower than 4.8.0.0 and the runtime is network-accessible with user authentication enabled.
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-released security patches for affected CODESYS products and restrict network access to minimize exposure to authenticated attackers.
CODESYS Control for SL version 4.8.0.0 or later (for your specific hardware platform)
- 1. Identify the specific CODESYS Control for SL product running on your device (e.g., Control for Raspberry Pi SL, Control for PFC200 SL, etc.)
- 2. Check the current installed version of the CODESYS product on your system
- 3. Obtain the fixed version 4.8.0.0 or later from the official CODESYS download page or your vendor's software distribution
- 4. Follow the standard CODESYS upgrade procedure: stop all running CODESYS Runtime services, backup your current project files and runtime configuration
- 5. Install version 4.8.0.0 or newer of the specific Control for SL product
- 6. After installation, restore your project files and runtime configuration from the backup
- 7. Restart the CODESYS Runtime services
- 8. Verify the installation was successful and the runtime is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47381 — 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-47381 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