CVE-2022-22517
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 unauthenticated, remote attacker can disrupt existing communication channels between CODESYS products by guessing a valid channel ID and injecting packets. This results in the communication channel to be closed.
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 denial-of-service vulnerability in CODESYS industrial automation products where an unauthenticated remote attacker can disrupt communication channels by guessing a valid channel ID and injecting malicious packets, causing the communication channel to close.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 productLocate the CODESYS Control runtime on the system; check system information, installed packages, or runtime documentation to determine which specific CODESYS Control variant is running (Beaglebone, Beckhoff CX9020, Empc, IoT2000, Linux, PFC100, PFC200, or PLCnext)Affected if The system runs any of the affected CODESYS Control variants listed in the CVE
-
Determine installed CODESYS versionAccess the CODESYS runtime version through the product interface, runtime diagnostics, or version check utility; common methods include checking the runtime web interface, examining runtime logs, or using the CODESYS development environment to query the target deviceAffected if The version number returned is below 4.5.0.0
-
Verify affected version rangeCompare the identified version against the affected range: any version < 4.5.0.0 for the listed CODESYS Control products is vulnerableAffected if The installed version is less than 4.5.0.0
-
Confirm network exposure of CODESYS communication portsCheck firewall rules and network configuration to determine if CODESYS communication ports (typically ports 1217, 1740, 1741, or vendor-specific ports) are accessible from untrusted networks; use netstat, nmap, or firewall configuration reviewAffected if CODESYS runtime ports are exposed to untrusted network segments without network segmentation or filtering
A system is affected if it runs any of the listed CODESYS Control products with a version number lower than 4.5.0.0 and has accessible communication ports.
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 patches when available; meanwhile, implement network segmentation and firewall rules to restrict unauthorized access to CODESYS communication ports, and monitor for anomalous packet injection attempts.
CODESYS Control version 4.5.0.0 or later for the respective platform (Control for Beaglebone, Beckhoff Cx9020, Empc A/imx6, IoT2000, Linux, PFC100, PFC200, or PLCnext)
- 1. Identify the specific CODESYS Control product (e.g., Control for Linux SL, Control for PFC200, etc.) currently deployed
- 2. Download CODESYS Control version 4.5.0.0 or later from the official CODESYS download repository (shop.codesys.com) or your customer portal
- 3. Review the migration/upgrade notes in the CODESYS Control installation guide for your specific hardware platform
- 4. Back up the current project configuration and runtime settings
- 5. Install the updated CODESYS Control runtime (version 4.5.0.0 or higher) on the target device following the hardware-specific upgrade procedure
- 6. Restore the configuration and verify the runtime is operational
- 7. Confirm the channel communication is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22517 — 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-22517 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