CVE-2022-4224
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 · uneditedIn multiple products of CODESYS v3 in multiple versions a remote low privileged user could utilize this vulnerability to read and modify system files and OS resources or DoS the device.
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 confidenceCODESYS v3 products contain a vulnerability allowing a remote low-privileged user to read and modify system files and OS resources, or cause denial of service. The vulnerability is exploitable over the network and affects multiple products and versions of the CODESYS v3 platform.
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>= 3.0, < 4.8.0.0>= 3.0, < 4.8.0.0>= 3.0, < 4.8.0.0>= 3.0, < 4.8.0.0>= 3.0, < 4.8.0.0>= 3.0, < 4.8.0.0>= 3.0, < 4.8.0.0>= 3.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 for CODESYS Control runtime packages or services on the system. Common locations include /opt/codesys, /etc/codesys, or package manager listings (dpkg -l, rpm -qa). Look for packages named 'codesys-control' or similar for your specific platform (Beaglebone, Raspberry Pi, Linux, IoT2000, PFC100, PFC200, PLCnext, Empc).Affected if A CODESYS Control runtime package is found on the system
-
Determine the installed versionRetrieve the version of the installed CODESYS Control runtime. For package-based installations, use the package manager query (dpkg -l <package_name> or rpm -qi <package_name>). For direct installations, check the runtime binary or configuration file version information, typically found in the installation directory under a version file or in the service executable metadata.Affected if The installed version is 3.0 or higher but lower than 4.8.0.0
-
Verify CODESYS runtime network service is activeCheck if the CODESYS Control runtime service is running and listening on network ports. Use 'netstat -tulpn' or 'ss -tulpn' to list active network listeners. CODESYS typically uses ports 11740, 11741, or 1217 (depending on configuration). Also check service status with 'systemctl status codesys-control' or similar service name for your variant.Affected if The runtime service is running and exposed on network interfaces accessible to untrusted users
-
Check network exposure of the management interfaceReview the CODESYS configuration file (typically 'CODESYSControl.cfg' or 'gateway.cfg' in /etc/codesys or the installation directory) for network binding settings. Verify whether the runtime is bound to interfaces reachable from untrusted networks. Use 'ip addr' or 'ifconfig' to identify all network interfaces and their addresses.Affected if The runtime is bound to 0.0.0.0 or an interface accessible from untrusted networks rather than localhost or isolated management networks
The system is affected if a CODESYS Control runtime for the listed platforms is installed with version 3.0 or higher but below 4.8.0.0, and the runtime service is running and 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-supplied patches for affected CODESYS v3 products and implement network segmentation to limit exposure of industrial control system interfaces to untrusted networks.
CODESYS Control version 4.8.0.0 or later for all affected product variants
- Obtain the CODESYS Control installation package for version 4.8.0.0 or later from the official CODESYS customer portal (customers.codesys.com)
- Verify the current installed version of CODESYS Control on the affected device
- Create a backup of the current project files and configuration
- Stop any running CODESYS Control runtime services before upgrading
- Install the updated CODESYS Control version 4.8.0.0 or newer following the standard installation procedure
- After installation, restart the CODESYS Control runtime services
- Verify the upgrade was successful by checking the installed version and testing basic functionality
- Review any new security settings or configurations introduced in the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4224 — 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-4224 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