CVE-2022-30791
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 CmpBlkDrvTcp of CODESYS V3 in multiple versions an uncontrolled ressource consumption allows an unauthorized attacker to block new TCP connections. Existing connections are not affected.
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 confidenceA denial-of-service vulnerability in the CmpBlkDrvTcp component of CODESYS V3 allows unauthenticated remote attackers to exhaust TCP connection resources, preventing legitimate new connections from being established. The attack targets the connection acceptance mechanism while leaving existing sessions unaffected.
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.6.0.0< 4.5.0.0< 4.5.0.0< 4.5.0.0< 4.6.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 CODESYS Control productCheck the device or runtime system for the installed CODESYS Control product name. This may be visible in the system information, runtime startup logs, or product-specific configuration files.Affected if The device runs any of the following: Codesys Control For Beaglebone, Empc A/imx6, Iot2000 Sl, Linux Sl, Pfc100 Sl, Pfc200 Sl, Plcnext, or Raspberry Pi Sl
-
Check installed CODESYS versionLocate and read the CODESYS runtime version information. On Linux-based devices, check /etc/codesys3/CODESYSControl.cfg or the runtime system info page. Compare the version number against the affected ranges: < 4.5.0.0 for Beaglebone, Empc, Linux, Pfc100, Pfc200, Raspberry Pi; < 4.6.0.0 for Iot2000 and Plcnext.Affected if The installed version is below 4.5.0.0 (for Beaglebone/Empc/Linux/Pfc100/Pfc200/Raspberry Pi) or below 4.6.0.0 (for Iot2000/Plcnext)
-
Verify CmpBlkDrvTcp component is loadedCheck if the CmpBlkDrvTcp component is present and active in the CODESYS runtime. This may be visible in the runtime configuration, component list, or system logs. The vulnerability exists specifically in this component.Affected if CmpBlkDrvTcp is enabled or loaded in the CODESYS runtime configuration
-
Inspect TCP listener configurationReview the CODESYS network configuration for TCP listener settings. Check for exposed TCP ports used by the CmpBlkDrvTcp component for accepting connections.Affected if TCP listeners configured by CmpBlkDrvTcp are exposed to untrusted networks
A system is affected if it runs any of the listed CODESYS Control products with a version below the threshold AND has the CmpBlkDrvTcp component enabled with accessible TCP listeners.
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.04.6.0.0
Apply the vendor-supplied CODESYS V3 patch to all affected installations; implement network-level rate limiting or source IP filtering as an interim control.
CODESYS Control products: upgrade to 4.5.0.0 or later (4.6.0.0 or later for Iot2000 Sl and Plcnext)
- 1. Identify the specific CODESYS Control product in use from the affected product list
- 2. Determine the current installed version of the Control runtime package
- 3. For products with versions < 4.5.0.0 (Beaglebone, Empc A/imx6, Linux Sl, Pfc100 Sl, Pfc200 Sl, Raspberry Pi Sl): upgrade to version 4.5.0.0 or later
- 4. For products with versions < 4.6.0.0 (Iot2000 Sl, Plcnext): upgrade to version 4.6.0.0 or later
- 5. Obtain the updated runtime package from the official CODESYS update channels or customers.codesys.com
- 6. Apply the update following the standard CODESYS runtime update procedure for the target device
- 7. After update, verify that new TCP connections can be established to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing24.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30791 — 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-30791 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