CVE-2022-32140
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 affected to a buffer overflow.A low privileged remote attacker may craft a request, which can cause a buffer copy without checking the size of the service, 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 confidenceA buffer overflow vulnerability exists in multiple CODESYS products where a low-privileged remote attacker can craft a request that performs a buffer copy without checking the size, leading to 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 productsLocate CODESYS Plcwinnt or CODESYS Runtime Toolkit on the system by checking installed programs, program directories, or runtime componentsAffected if Either product is present on the system
-
Determine the Plcwinnt versionCheck the version of the Codesys Plcwinnt installation (typically found in program files, product documentation, or system information)Affected if The installed version is 2.0 or higher but lower than 2.4.7.57
-
Determine the Runtime Toolkit versionCheck the version of the Codesys Runtime Toolkit installation (check runtime component files, product documentation, or system information)Affected if The installed version is 2.0 or higher but lower than 2.4.7.57
-
Confirm remote access is enabledVerify that remote network communication or CaaS (Communication as a Service) features are enabled in the CODESYS configuration, as the vulnerability is exploitable remotelyAffected if Remote access features are enabled and the version falls within the affected range
The system is affected if either CODESYS Plcwinnt or Runtime Toolkit version is >= 2.0 and < 2.4.7.57 with remote access capabilities available.
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 available vendor patches for affected CODESYS products when released. Until patches are available, implement network segmentation and restrict access to affected systems to minimize attack surface.
2.4.7.57 or later
- Identify the installed CODESYS product (Plcwinnt or Runtime Toolkit) and current version
- Backup current configuration and project data
- Upgrade Plcwinnt to version 2.4.7.57 or later, OR upgrade Runtime Toolkit to version 2.4.7.57 or later
- Verify the upgrade was successful by checking the product version
- Test that affected services start and operate normally
- Monitor for any anomalies
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32140 — 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-32140 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