dbcve.org
PlcwinntApplication · Codesys

CVE-2022-32143

HIGH · 8.8 CVSS v3.1 Published 2022-06-24
Fix available
A fix is available. Upgrade to 2.4.7.57 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
In multiple CODESYS products, file download and upload function allows access to internal files in the working directory e.g. firmware files of the PLC. All requests are processed on the controller only if no level 1 password is configured on the controller or if remote attacker has previously successfully authenticated himself to the controller. A successful Attack may lead to a denial of service, change of local files, or drain of confidential Information. 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 confidence

Multiple CODESYS products contain an improper access control vulnerability in the file download/upload functionality. Attackers can access internal files in the working directory (including PLC firmware files) without proper authentication when no level 1 password is configured on the controller or if the attacker has previously authenticated. This can lead to denial of service, modification of local files, or exfiltration of confidential information.

MitigationConfigure a strong level 1 password on all CODESYS controllers to enforce proper authentication. If remote access is required, ensure network segmentation and firewall rules limit exposure to trusted networks only.

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
PlcwinntApplication
Affected:>= 2.0, < 2.4.7.57
Runtime ToolkitApplication
Affected:>= 2.0, < 2.4.7.57

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed CODESYS version
    Locate the CODESYS Plcwinnt or Runtime Toolkit installation directory and check the version information (typically in product info, about dialog, or version file within the installation folder). Compare against the affected range: >= 2.0, < 2.4.7.57
    Affected if The installed version falls within 2.0 to 2.4.7.56 inclusive (any version >= 2.0 but less than 2.4.7.57)
  2. Check if level 1 password is configured
    Access the CODESYS controller configuration or runtime settings and inspect whether a level 1 (user) password has been set. This is typically found in the controller's security settings, user management, or password configuration panel within the CODESYS development environment or runtime configuration.
    Affected if No level 1 password is configured on the controller (the password field is empty or unset)
  3. Verify file download/upload feature exposure
    Determine if the file download/upload functionality is accessible on the controller. This may involve checking the runtime configuration, network services enabled on the controller, or reviewing the CODESYS web server/file server settings if present.
    Affected if File download/upload functionality is enabled and accessible without authentication requirement

You are affected if your CODESYS Plcwinnt or Runtime Toolkit version is between 2.0 and 2.4.7.56 AND either no level 1 password is configured or the file download/upload feature is accessible without proper authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.4.7.57 or later
Fixed in 2.4.7.57
Interim mitigation

Configure a strong level 1 password on all CODESYS controllers to enforce proper authentication. If remote access is required, ensure network segmentation and firewall rules limit exposure to trusted networks only.

Recommended fix High confidence

2.4.7.57 or later

  1. 1. Identify the current installed version of Plcwinnt or Runtime Toolkit on the affected system
  2. 2. Download CODESYS version 2.4.7.57 or later from the official vendor source (customers.codesys.com)
  3. 3. Review the vendor's upgrade documentation and release notes before proceeding
  4. 4. Perform a backup of the current configuration and project files
  5. 5. Stop all running CODESYS services and PLC applications
  6. 6. Install the updated version following the vendor's standard upgrade procedure
  7. 7. After upgrade, verify the installation was successful
  8. 8. Configure a level 1 password on the controller as an additional security measure, per the vendor's security recommendations
Caveat No specific breaking changes documented in provided material; standard upgrade precautions apply (backup before upgrade)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Plcwinnt Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32143 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-32143 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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