CVE-2022-47379
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 out-of-bounds write vulnerability in multiple CODESYS products in multiple versions to write data into memory 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 an out-of-bounds write vulnerability in multiple CODESYS products. An authenticated remote attacker can exploit improper memory boundary checks to write data beyond allocated buffers, leading to memory corruption that can cause denial of service, memory overwriting, 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 productCheck the system for installed CODESYS Control software packages. Common locations: /etc/codesys, /opt/codesys, or check installed packages via package manager (dpkg -l, rpm -qa). Look for product names matching 'CODESYS Control' for Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi.Affected if Any CODESYS Control product from the affected list is installed on the system
-
Determine the specific product variantInspect the product name or package identifier. The affected products are: Codesys Control For Beaglebone Sl, Codesys Control For Empc A/imx6 Sl, Codesys Control For IoT2000 Sl, Codesys Control For Linux Sl, Codesys Control For Pfc100 Sl, Codesys Control For Pfc200 Sl, Codesys Control For Plcnext Sl, Codesys Control For Raspberry Pi Sl.Affected if The installed product matches any of these eight product names
-
Check installed version numberQuery the installed CODESYS Control version. Common methods: check the product's about dialog, run 'codesysinfo' or similar utility, read version from installation metadata files (package.json, MANIFEST.MF, or version.info in the installation directory), or check the Windows registry on Windows-based installations.Affected if The installed version is lower than 4.8.0.0 (for example: 4.7.x, 4.6.x, 3.x series)
-
Verify remote access is enabledCheck if the CODESYS Control runtime is configured to accept remote connections. Inspect network configuration files (CODESYSControl.cfg, gateway settings), check if the runtime service is listening on network interfaces (netstat -anp | grep codesys), and verify the SP 'Communication Settings' in the development environment.Affected if Remote/network communication is enabled and the service is accessible over the network
The environment is affected if a CODESYS Control product from the list is installed with a version below 4.8.0.0 and has network communication 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-supplied security patches for all affected CODESYS products, enforce network segmentation to limit exposure, and ensure strong authentication controls are in place for affected systems.
CODESYS Control products version 4.8.0.0 or later
- Identify the specific CODESYS Control product in use from the affected list (Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi)
- Locate the current installed version of the CODESYS Control product
- Verify the current version is below 4.8.0.0
- Obtain the fixed version 4.8.0.0 or later from the official CODESYS download repository at customers.codesys.com
- Create a complete backup of the current project and configuration
- Test the upgrade in a non-production/staging environment first
- Apply the upgrade following standard CODESYS software update procedures
- Verify the new version is 4.8.0.0 or higher after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47379 — 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-47379 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