CVE-2022-32136
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 CODESYS products, a low privileged remote attacker may craft a request that cause a read access to an uninitialized pointer, resulting in a denial-of-service. User interaction is not required.
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 confidenceIn multiple CODESYS products, a low-privileged remote attacker can send a specially crafted request that triggers a read from an uninitialized pointer, causing the application to crash and resulting in a denial-of-service condition. No user interaction is required for exploitation.
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>= 2.0, < 2.4.7.57>= 2.0, < 2.4.7.57CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 productsCheck system for presence of Codesys Plcwinnt or Codesys Runtime Toolkit components. Look in installed programs list or product documentation to confirm which CODESYS products are deployed.Affected if Either Codesys Plcwinnt or Codesys Runtime Toolkit is installed
-
Determine Plcwinnt versionLocate the installed version of Codesys Plcwinnt. This is typically found in the product's about dialog, version information in the executable, or installation directory metadata.Affected if Version is >= 2.0 and < 2.4.7.57
-
Determine Runtime Toolkit versionLocate the installed version of Codesys Runtime Toolkit. Check product documentation, runtime system information, or version details in the installation directory.Affected if Version is >= 2.0 and < 2.4.7.57
-
Assess network exposureDetermine if the CODESYS product is accessible from network segments accessible to untrusted users. Review firewall rules and network ACLs protecting the affected system.Affected if Product is network-accessible without proper segmentation from untrusted networks
The environment is affected if Codesys Plcwinnt or Codesys Runtime Toolkit version is 2.0 or higher but below 2.4.7.57, and the product 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 · scoped2.4.7.57
Apply vendor-supplied patches or updates for affected CODESYS products. If patches are unavailable, network segmentation and access controls should be implemented to limit exposure to untrusted networks.
2.4.7.57 or later
- 1. Identify all deployed instances of Plcwinnt and Runtime Toolkit products in your environment
- 2. Check the current version of each installed product
- 3. If the version is >= 2.0 and < 2.4.7.57, the system is vulnerable
- 4. Obtain the updated version 2.4.7.57 or later from the CODESYS customer portal at customers.codesys.com
- 5. Schedule a maintenance window for the update
- 6. Backup all current configurations before proceeding with the upgrade
- 7. Apply the upgrade to all affected Plcwinnt and Runtime Toolkit installations
- 8. After upgrading, verify the new version is 2.4.7.57 or later
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-32136 — 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-32136 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