CVE-2022-22515
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 · uneditedA remote, authenticated attacker could utilize the control program of the CODESYS Control runtime system to use the vulnerability in order to read and modify the configuration file(s) of the affected products.
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 confidenceThis vulnerability in the CODESYS Control runtime system allows a remote, authenticated attacker to read and modify configuration files through the control program interface. The vulnerability indicates improper access control or authorization validation in the configuration file handling mechanism of the runtime system.
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.5.0.0< 4.5.0.0< 4.5.0.0< 4.5.0.0< 4.5.0.0< 4.5.0.0< 4.5.0.0< 4.5.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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 installed CODESYS Control runtime productLocate the CODESYS Control installation directory or check system information for the specific runtime name such as 'CODESYS Control for Linux', 'CODESYS Control for Beaglebone', 'CODESYS Control for Beckhoff CX9020', 'CODESYS Control for PFC200', or other variants from the affected product listAffected if The installed product matches one of the affected products: Beaglebone SL, Beckhoff CX9020, Empc A/imx6 SL, IoT2000 SL, Linux SL, PFC100 SL, PFC200 SL, or PLCnext SL
-
Determine the installed version numberCheck the version of the CODESYS Control runtime - this is typically found in the product's 'About' dialog, in the installation directory's version info, or via the CODESYS Development System when connected to the runtimeAffected if The version is lower than 4.5.0.0 for any of the affected products listed
-
Verify if the control program interface (CMP) is enabled and accessibleCheck the CODESYS Control runtime configuration for enabled network interfaces or protocols that expose the control program interface - this is typically found in the runtime's configuration file or web-based management interfaceAffected if The control program interface is enabled and bound to a network address that is accessible from remote locations
-
Confirm network exposure of the runtimeInspect network configuration or firewall rules to determine if the CODESYS Control runtime's communication ports (typically TCP ports 1217, 11740, or similar) are exposed to untrusted networksAffected if The runtime is accessible from network segments that include untrusted or attacker-controlled systems
A user is affected if they have any of the eight listed CODESYS Control runtime products installed with version lower than 4.5.0.0 and the control program interface is network-accessible.
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.5.0.0
Apply vendor-provided patches or updates for CODESYS Control runtime systems. If no patch is available, restrict network access to the control program interface and enforce strong authentication controls.
CODESYS Control runtime version 4.5.0.0 or later
- 1. Back up all existing CODESYS Control project files and configurations before upgrading
- 2. Download the CODESYS Control runtime version 4.5.0.0 or later from the official CODESYS website or your vendor's portal (customers.codesys.com)
- 3. Verify the downloaded package matches your specific hardware platform (Beaglebone, Beckhoff Cx9020, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, or Plcnext)
- 4. Follow the vendor-specific installation instructions for your hardware platform
- 5. After installation, verify the new version is running by checking the CODESYS Control runtime version
- 6. Test that existing control applications function correctly with the new runtime version
- 7. Review configuration files to ensure they were properly migrated and retain intended settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22515 — 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-22515 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