CVE-2022-32141
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 · uneditedMultiple CODESYS Products are prone to a buffer over read. A low privileged remote attacker may craft a request with an invalid offset, which can cause an internal buffer over-read, resulting in a denial-of-service condition. 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 confidenceMultiple CODESYS products contain a buffer over-read vulnerability where a low-privileged remote attacker can craft a request with an invalid offset, causing an internal buffer over-read that results in denial-of-service conditions without requiring user interaction.
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 productLocate the CODESYS installation directory or list installed software packages. Look for either 'Plcwinnt' or 'Runtime Toolkit' components.Affected if Either Plcwinnt or Runtime Toolkit is installed
-
Check installed version numberOpen the product's version information dialog, check the About section in the CODESYS development environment, or examine the version metadata in the installation directory. Compare against the affected range.Affected if Installed version is 2.0 or higher but lower than 2.4.7.57
-
Verify network accessibility of the serviceDetermine if the CODESYS runtime service is listening on network ports. Check network configuration and firewall rules for the service.Affected if The CODESYS service is exposed to network access from untrusted sources
User is affected if Plcwinnt or Runtime Toolkit version is between 2.0 and 2.4.7.56 inclusive, and the service is network-accessible to remote attackers.
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-provided patches for affected CODESYS products and implement proper input validation on offset values in the affected components to prevent buffer over-read conditions.
Upgrade to version 2.4.7.57 or later for both Plcwinnt and Runtime Toolkit
- 1. Identify which CODESYS product is affected: Plcwinnt or Runtime Toolkit
- 2. Check the current installed version of the affected product
- 3. Obtain the updated version 2.4.7.57 or later from CODESYS (e.g., from customers.codesys.com or official distribution channels)
- 4. Apply the update following standard CODESYS upgrade procedures
- 5. Verify the version has been successfully updated to 2.4.7.57 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.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,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32141 — 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-32141 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