dbcve.org
GatewayApplication · Codesys

CVE-2022-31802

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-24
Fix available
A fix is available. Upgrade to 2.3.9.38 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 CODESYS Gateway Server V2 for versions prior to V2.3.9.38 only a part of the the specified password is been compared to the real CODESYS Gateway password. An attacker may perform authentication by specifying a small password that matches the corresponding part of the longer real CODESYS Gateway password.

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 · high confidence

CODESYS Gateway Server V2 versions prior to V2.3.9.38 contain a partial password comparison vulnerability in the authentication mechanism. The server only validates a substring of the provided password against the corresponding prefix of the stored password, allowing authentication with a shorter password that matches the beginning portion of the actual password.

MitigationUpgrade CODESYS Gateway Server V2 to version V2.3.9.38 or later to implement full password comparison.

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
GatewayApplication
Affected:>= 2.0, < 2.3.9.38

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 CODESYS Gateway Server V2 installation
    Locate the CODESYS Gateway Server V2 installation directory or executable (typically in C:\Program Files\CODESYS\GatewayServer or similar). Right-click the GatewayServer.exe file and select Properties > Details to view the File Version.
    Affected if CODESYS Gateway Server V2 is installed on the system
  2. Determine installed version
    Note the File Version shown in the Details tab. This corresponds to the CODESYS Gateway version. Compare this version number to the affected range.
    Affected if The installed version is 2.0 or higher but lower than 2.3.9.38
  3. Confirm server is using password authentication
    Check if the CODESYS Gateway Server is configured to require password authentication for client connections. This can be verified through the CODESYS configuration or by reviewing the server's authentication settings.
    Affected if The server accepts password-based authentication and the version is within the affected range

If CODESYS Gateway Server V2 is installed with a version between 2.0 and 2.3.9.38 (inclusive of 2.0 but exclusive of 2.3.9.38), the environment is affected by the partial password comparison vulnerability.

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.3.9.38 or later
Fixed in 2.3.9.38
Interim mitigation

Upgrade CODESYS Gateway Server V2 to version V2.3.9.38 or later to implement full password comparison.

Recommended fix High confidence

CODESYS Gateway Server V2 version 2.3.9.38 or later

  1. Identify all CODESYS Gateway Server V2 instances in the environment
  2. Check current version of each Gateway installation (must be >= 2.0 and < 2.3.9.38)
  3. Obtain the updated CODESYS Gateway Server V2 version 2.3.9.38 or later from the official vendor (CODESYS customer portal at customers.codesys.com)
  4. Schedule a maintenance window for each affected Gateway
  5. Back up current Gateway configuration and any associated data
  6. Install version 2.3.9.38 or later of CODESYS Gateway Server V2
  7. Verify the upgrade was successful and the Gateway starts correctly
  8. Test that authentication works properly with full password validation

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

Fix this in Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31802 — 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-31802 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