CVE-2022-32139
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, which cause an out-of-bounds 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 confidenceIn multiple CODESYS products, a low-privileged remote attacker can send a crafted request that triggers an out-of-bounds memory read, causing a denial-of-service condition 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 productsCheck the system for CODESYS Plcwinnt or CODESYS Runtime Toolkit installations. Look in program files, common installation directories, or check installed programs list.Affected if Either product is installed on the system
-
Determine installed version of CODESYS PlcwinntCheck the product version in the Windows Programs and Features list, or right-click on the executable and view Properties > Details for version information.Affected if Version is 2.0 or higher but lower than 2.4.7.57
-
Determine installed version of CODESYS Runtime ToolkitCheck the product version in the Windows Programs and Features list, or check version info in the runtime toolkit binaries or associated manifest files.Affected if Version is 2.0 or higher but lower than 2.4.7.57
-
Verify network exposure of CODESYS servicesCheck if CODESYS runtime or control services are listening on network ports. Use 'netstat -an' or similar network scanning tools to identify listening services associated with CODESYS.Affected if CODESYS network services are directly accessible from untrusted network segments
The system is affected if either CODESYS Plcwinnt version 2.0 to 2.4.7.56 or CODESYS Runtime Toolkit version 2.0 to 2.4.7.56 is installed and has network-facing services exposed.
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 patches or updates provided by CODESYS for affected products; if no patch exists, implement network segmentation and restrict remote access to minimize attack surface.
2.4.7.57
- 1. Identify whether the affected system is running Plcwinnt or Runtime Toolkit from CODESYS
- 2. Check the currently installed version of the affected component
- 3. Download the fixed version 2.4.7.57 or later from the official CODESYS source (customers.codesys.com)
- 4. Apply the upgrade following standard CODESYS update procedures
- 5. Verify the installation of the patched version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32139 — 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-32139 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